- NANOG - lists.nanog.org

Sprint BGP filters in 207.x.x.x?
by Avi Freedman 17 Dec '95

17 Dec '95

What's the smallest CIDR block Sprint will listen to from an external source in the 207.x.x.x-208.x.x.x range? Is it different than the filters on > /19s in 206.x.x.x-207.x.x.x range? Avi

11 22

Re: Routing registry was Re: Sprint BGP filters in 207.x.x.x?
by Jeff.Ogden＠um.cc.umich.edu 17 Dec '95

17 Dec '95

The large scale provider MichNet uses is MCI and they are required to cooperate with the RA and others. This is in their contract. I suspect that something similar might be in some of the other contracts of providers that provide service to networks that received funding from NSF for Interregional Connectivity. People might want to go read the fine print in their contracts. -Jeff Ogden Merit/MichNet

4 3

Re: Routing registry was Re: Sprint BGP filters in 207.x.x.x? (fwd)
by Elise Gerich 14 Dec '95

14 Dec '95

Peter, >Peter Lothberg writes: > > [stuff deleted] > > The RA is broken, just relabeling work of Ripe and mess it upp is > not very usefull for the Global Internet. Ripe-81 (that most of this > is based on) was supposed to be a start of a toolkit for ISP's, not a > tol for someone who think they are the network Police. > > -Peter > We've had this discussion many times, and will probably never agree. The RA adopted the RIPE database work since it seemed reasonable to express global information in a standard fashion. Credit is given to RIPE and the PRIDE project whenever there is talk of the IRR, RIPE NCC Database, the RADB, etc. The RA team has announced many tools based on the database and the routes known to the route servers: 1) IRRWeb - graphical interface to query the IRR and to update the RADB 2) Route History Server - provides a mechanism for tracking the announce/ withdraw history of a given prefix for the last 24 hours 3) Route Flap Statistics Generator - provides mechanism for calculating the level of routing instability at all of the four NAPs 4) Route Server Routing Table Statistics Generator - reports on the size an content of the Internet routing tables as seen by the Route Servers at each Network Access Point 5) Peval - policy evaluator that inputs RIPE-181 policy expression, performs certain calculations, and outputs expressions that can be used by other tools, like RTConfig 6) RTConfig - front-end tool that uses Peval and RADBserver to generate router configurations 7) RADBserver - extension of the RIPE whoisd server which provides a protocol for getting information from RIPE-style database files 8) RSd - an enhanced version of GateD routing software that provides multiple views of routing information 9) rrc2r/rrmerge - a package to convert Cisco router configuration files to RIPE-181 objects that can be submitted to a RIPE-style database 10) CiscoBGP - analyzes routing information from production Ciscos and compares the data with routes in the IRR 11) BGPCheck - compares information from BGP4 peering sessions with the route serves with data in the IRR 12) PRtraceroute - developed by the PRIDE project, the RA team provides a version that queries the RADB In addition if you look at the RA web pages, you will find descriptions of other tools which are under development. The RA is committed to working with the community to develop tools that are seen as beneficial. --Elise (does NOT rhyme with police)

1 0

CERT Vendor-Initiated Bulletin VB-95:09 - Hewlett-Packard
by CERT Bulletin 14 Dec '95

14 Dec '95

CERT Vendor-Initiated Bulletin VB-95:09 December 14, 1995 Topic: Security vulnerability in ftp in releases 9.X and 10.X of HP-UX Source: Hewlett-Packard Company To aid in the wide distribution of essential security information, the CERT Coordination Center is forwarding the following information from Hewlett-Packard. HP urges you to act on this information as soon as possible. HP contact information is included in the forwarded text below; please contact them if you have any questions or need further information. ========================FORWARDED TEXT STARTS HERE============================ - ------------------------------------------------------------------------- HEWLETT-PACKARD SECURITY BULLETIN: HPSBUX9511-028, 28 Nov 95 - ------------------------------------------------------------------------- Hewlett-Packard recommends that the information in the following Security Bulletin should be acted upon as soon as possible. Hewlett- Packard will not be liable for any consequences to any customer resulting from customer's failure to fully implement instructions in this Security Bulletin as soon as possible. _______________________________________________________________________ PROBLEM: Security vulnerability in ftp in releases 9.X and 10.X of HP-UX PLATFORM: HP 9000 series 300/400s and 700/800s DAMAGE: A vulnerability in ftp behavior exists which involves ftp server bouncing. This is a cumulative ftp(1) and ftpd(1M) patch. SOLUTION: Apply patch PHNE_6013 (series 700/800, HP-UX 9.x), or PHNE_6014 (series 700/800, HP-UX 10.x), or PHNE_6146 (series 300/400, HP-UX 9.x), or PHNE_6170 (series 700, HP-UX 9.09), or PHNE_6169 (series 700, HP-UX 9.09+), or PHNE_6171 (series 800, HP-UX 9.08) PHNE_5965 (series 700, HP-UX 10.09) AVAILABILITY: All patches are available now, except for the 9.0X BLS patches which will be available after January 2, 1996. _______________________________________________________________________ I. Update A. Vulnerability The vulnerability allows users to exploit ftp. If these patches are properly installed, the vulnerability cannot be exploited. It has been found that all HP-UX systems have this vulnerability. B. Fixing the problem The vulnerability can be eliminated from releases 9.x and 10.x of HP-UX by applying a patch. To treat only the commercial releases of HP-UX prior to 9.x, administrators should make plans to upgrade their systems to a currently supported release listed above. Hewlett-Packard recommends that all customers concerned with the security of their HP-UX systems apply the appropriate patch described above as soon as possible. Side effects: none. C. How to Install the Patch (for HP-UX 9.x and 10.x) 1. Determine which patch is appropriate for your hardware platform and operating system: For the Commercial HP-UX releases: PHNE_6013 (series 700/800, HP-UX 9.x), or PHNE_6014 (series 700/800, HP-UX 10.x), or PHNE_6146 (series 300/400, HP-UX 9.x). For the BLS HP-UX releases: PHNE_6169 (series 700, HP-UX 9.09+), or PHNE_6170 (series 700, HP-UX 9.09), or PHNE_6171 (series 800, HP-UX 9.08), or PHNE_5965 (series 700, HP-UX 10.09). The three 9.0x B Level Security (BLS) patches will be available after January 2, 1996. 2. Hewlett Packard's HP-UX patches are available via email and World Wide Web. To obtain a copy of the HP SupportLine email service user's guide, send the following in the TEXT PORTION OF THE MESSAGE to support(a)us.external.hp.com (no Subject is required): send guide The user's guide explains the process for downloading HP-UX patches via email and other services available. World Wide Web service for downloading of patches is available via our URL: (http://us.external.hp.com/) 3. Apply the patch to your HP-UX system. 4. Examine /tmp/update.log for any relevant WARNINGs or ERRORs. This can be done as follows: a. At the shell prompt, type "tail -60 /tmp/update.log | more" b. Page through the next three screens via the space bar, looking for WARNING or ERROR messages. D. Impact of the patch and workaround The patch for HP-UX releases 9.x and 10.x provides a new version of /usr/bin/ftp and /etc/ftpd which fixes the vulnerability. No patches will be available for versions of HP-UX prior to 9.0. To protect those affected systems, we recommend upgrading to a currently supported release of HP-UX. E. To subscribe to automatically receive future NEW HP Security Bulletins from the HP SupportLine mail service via electronic mail, send an email message to: support(a)us.external.hp.com (no Subject is required) Multiple instructions are allowed in the TEXT PORTION OF THE MESSAGE, here are some basic instructions you may want to use: To add your name to the subscription list for new security bulletins, send the following in the TEXT PORTION OF THE MESSAGE: subscribe security_info To retrieve the index of all HP Security Bulletins issued to date, send the following in the TEXT PORTION OF THE MESSAGE: send security_info_list To get a patch matrix of current HP-UX and BLS security patches referenced by either Security Bulletin or Platform/OS, put the following in the text portion of your message: send hp-ux_patch_matrix World Wide Web service for browsing of bulletins is available via our URL: (http://us.external.hp.com/) Choose "Support news", then under Support news, choose "Security Bulletins" F. To report new security vulnerabilities, send email to security-alert(a)hp.com _______________________________________________________________________ ============================================================================== ***HP SupportLine Mail Service Notice*** This digest contains a summary of all newly received Security Bulletins. You do not have to have any form of support from Hewlett-Packard to subscribe to this digest or to procure the recommended patches via the HP SupportLine mail service. - ---------------------------------------------------------------------------- To obtain a copy of the HP SupportLine mail service user's guide, send the following (in the TEXT PORTION OF THE MESSAGE to) to the HP SupportLine mail service. To: support(a)us.external.hp.com Message Text: send guide - ---------------------------------------------------------------------------- To obtain a patch identified within this Security Bulletin, send the following (in the TEXT PORTION OF THE MESSAGE) to the HP SupportLine mail service. To: support(a)us.external.hp.com Message Text: send xxxxxxxxxxxx (where xxxxxxxxxxxx represents the specified patch name). - ---------------------------------------------------------------------------- If you have concerns about security issues, please forward them to: security-alert(a)hp.com The security-alert node is monitored during working hours Pacific Daylight Time by multiple HP Security Response Team personnel. We reply to your message only if necessary to obtain additional information. - ---------------------------------------------------------------------------- If you would like to be REMOVED from this mailing lists, send the following (in the TEXT PORTION OF THE MESSAGE) to the HP SupportLine mail service. To: support(a)us.external.hp.com Message Text: unsubscribe security_info =========================FORWARDED TEXT ENDS HERE============================= CERT publications, information about FIRST representatives, and other information related to computer security are available for anonymous FTP from info.cert.org. CERT advisories and bulletins are also 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. If you wish to send sensitive incident or vulnerability information to CERT staff by electronic mail, we strongly advise that the e-mail be encrypted. The CERT Coordination Center can support a shared DES key, PGP (public key available via anonymous FTP on info.cert.org) or PEM (contact CERT staff for details). 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 CERT Coordination Center Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 USA CERT is a service mark of Carnegie Mellon University.

1 0

Re: Routing registry was Re: Sprint BGP filters in 207.x.x.x?
by Jeff.Ogden＠um.cc.umich.edu 14 Dec '95

14 Dec '95

MichNet's agreement is with MCI. I can't speak about deals others may have with Sprint. I think it is unlikely that Sprint got any Interregional Connectivity money, however. That money went to regional networks. Those networks may be spending some of the NSF funds with Sprint. The agreements that came from NSF along with the money imposed requirements on the regional networks and not directly on the NSPs. It is up to the regional networks to pass those requirements on to their NSP and I'd think it was up to the regional networks and not NSF to see that the NSPs follow the requirements. Sprint is a funny beast in this discussion because they are both an NSP and a NAP operator (and still the International Connections Manager?), but I think the recent discussion has been talking about NSPs and not NAP operators. -Jeff Ogden Merit

2 1

unsuscribe
by Peter deBlanc 14 Dec '95

14 Dec '95

unsuscribe

1 0

Re: routing problem
by Joe Pruett 13 Dec '95

13 Dec '95

i was trying to keep the message short, and i probably elided a bit too much. we're just using bgp for outgoing routing, no load balancing. we've made sure that as3838 isn't filtering, and their upstream providers (alternet and agis) claim to not be filtering, either.

1 0

routing problem
by Joe Pruett 13 Dec '95

13 Dec '95

i hope this is appropriate for this list. 192.108.254.0/24 is being announced from as5798 via as3130 and as3838. we have an radb entry for it. there was an mci entry until monday night. but as of today (wednesday) we still get all incoming traffic via as3130. outgoing seems to be fairly well balanced between our providers, so the theory says that we should get about equal data in from them too. maybe some of you can look at your routers and help me figure out why we aren't getting any data in via as3838. any other clues would be greatly appreciated as well.

2 1

Re: Sprint BGP filters in 207.x.x.x?
by Ted Linnenkamp 13 Dec '95

13 Dec '95

Message-ID: red-13-msg951213213258MTP[01.51.00]000000ac-28766 MCI announces smaller routes for its customers that do not use the CIDR blocks given to MCI. If you brought address space to MCI they would announce it. The most important thing is that on NEW CIDR blocks they stay aggregated. This is why Sprint will not listen to the announcement of /18 or less address space in the 207.xx/8 block. Painful but effective. Ted L. ---------- From: Jon Zeeff <jon(a)branch.com> To: <cook(a)cookreport.com> Cc: <dmbarton(a)mci.net>; <smd(a)chops.icp.net>; <freedman(a)netaxs.com>; <nanog(a)merit.edu> Subject: Re: Sprint BGP filters in 207.x.x.x? Date: Wednesday, December 13, 1995 1:17PM I think this is misleading. MCI does announce routes smaller than this for its customers. > MCI aggregates all its customer's routes into /19's. We have just

1 0

Re: chicago nap questions
by reb＠aads.net 13 Dec '95

13 Dec '95

> At 8:16 PM 12/7/95, Gordon Cook wrote: > > went looking for aadsnet on ameritechs chicago nap web page > > couldn't find them. But shouldn't they be there to get the rest of their > customers to the rest of the internet? AADSNet does not use the NAP for connectivity to the Internet for it's Chicago LATA customers. eric ---- R. Eric Bennett <reb(a)aads.net> | 339 E. Liberty, Suite 310 Internet Engineering | Ann Arbor, MI 48014 Ameritech Advanced Data Services | (313) 913-0802 "We're from the phone company, we're here to help."

1 0