Hi good people,
Does anybody have real-world experince running 5400's as pure ISDN PRI
concentrator? Of real interest are the following areas:
1. BGP support: features and stability, compared say to 12.0S on 7200's?
2. How many PRI cards will box take, provided *no* digital modems are
installed?
3. How good is multilink PPP support and stability, especially of larger
multilink bundles, say from 2 to 8 B-channels?
4. What is the recommended IOS version to use? 12.2 would be nice (probably
12.2XA?), because we will need "user max-links" support.
Thanks,
-- CCNP, CCDP (R&S) Dmitri E. Kalintsev CDPlayer@irc Network Architect @ connect.com.au dek @ connect.com.au phone: +61 3 9674 3913 fax: 9251 3666 http://-UNAVAIL- UIN:7150410 mobile: +61 414 821 382From gsanchez@servicõÅ;00Received: from someone claiming to be truth.servicom2000.com (qmailr@truth.servicom2000.cõÅ;21 by puck.nether.net (8.11.4/8.9.3) with SMTP id f6CCteA03649 for <cisco-nsp@puck.nether.net>; Thu, 12 Jul 2õÅ;08 (envelope-from gsanchez@servicom2000.com) Received-Date: Thu, 12 Jul 2001 08:55:40 -0400 Received: (qmail 28õÅ;inReceived: from top.servicom2000.com (HELO PCGabi) (212.101.64.178) by trõÅ;seMessage-ID: <001301c10ad2$2c0f61a0$bc01a8c0@PCGabi> From: "Gabriel SaõÅ;z"To: <cisco-nsp@puck.nether.net> Date: Thu, 12 Jul 2001 14:57:13 +0200 MIME-Version: 1.0 ConteõÅ;yp boundary="----=_NextPart_000_000F_01C10AE2.EF7FC7A0" X-Priority: 3 X-MSMail-Priority: Normal X-MailerõÅ;crX-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Subject: [nsp] Access lists õÅ;up
This is a multi-part message in MIME format.
------=_NextPart_000_000F_01C10AE2.EF7FC7A0 Content-Type: mulõÅ;rt boundary="----=_NextPart_001_0010_01C10AE2.EF7FC7A0"
------=_NextPart_001_0010_01C10AE2.EF7FC7A0 Content-õÅ;: charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
2 VLANs (Bridge-group 9 and 10)
*-------- õÅ;G-
2948G-L3 config
....
ip uplink-redirect
bridge irb
!
....
õÅ;rf
no ip address
no ip directed-broadcast
no cdp enable
bridge-group 9
bridge-group 9 spanning-disableõÅ;
iNterface FastEthernet7
no ip address
no ip directed-broadcast
no cdp enable
bridge-group 10
bridge-group 10 spõÅ;ng
!
....
interface GigabitEthernet49
ip address 192.168.20.253 255.255.255.252
ip access-group telnet in
no õÅ;ir
no cdp enable
!
....
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.20.254
!
......
ip access-list õÅ;nd
permit tcp host 212.101.75.10 host 212.101.75.2 eq telnet
As you can see in the previous config, I have to comõÅ;cain a 2948G-L3 working in an "uplink-redirect" environment with a = 4908G-L3 as router.=20
All works fine; õÅ;ngaddress in the 4908G and return again to the other VLAN in the 2948, but = õÅ;oo2948, as you can see in the configuration, I can't communiõÅ; bthe two VLANs. Although the ACL is a "permit", all the traffic is = blocked.
Has anyone installed access-lists iõÅ;is
I'll appreciate any help.
=20
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virõÅ;ysVersion: 6.0.263 / Virus Database: 135 - Release Date: 22/06/01
------=_NextPart_001_0010_õÅ;0AContent-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBõÅ;"-<HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-õÅ;-1<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT fõÅ;3D<P>2 VLANs (Bridge-group 9 and 10)</P> <P>*-------- 2948G-L3 -----------* -ÑëÅ;t-<P>....</P> <P>ip uplink-redirect</P> <P>bridge irb<õÅ;<P P>....</P> <P>interface FastEthernet1</P> <P>no ip address</P> <P>no ip directed-broadcast</P> <P>no cdp enable</PõÅ;>b<P>bridge-group 9 spanning-disabled</P> <P>!</P> <P>....</P> <P>interface FastEthernet7</P> <P>no ip addõÅ;</<P>nO ip directed-broadcast</P> <P>no cdp enable</P> <P>bridge-group 10</P> <P>bridge-group 10 spanning-disabled</P> <PõÅ;P><P>interface GigabitEthernet49</P> <P>ip address 192.168.20.253 255.255.255.252</P> <P>ip access-group telnetõÅ;/P<P>no cdp enable</P> <P>!</P> <P>....</P> <P>ip classless</P> <P>ip route 0.0.0.0 0.0.0.õÅ;2.<P>!</P> <P>......</P> <P>ip access-list extended telnet</P> <P>permit tcp host 212.101.75.10 host 212.101.õÅ; e<P>As you can see in the previous config, I have to communicate two = VLANs in a=20 2948G-L3 working in an "uÑëÅ;k-<P>All works fine; a ping goes from a VLAN in the 2948, toõÅ; =address in the 4908G and return again to the other VLAN in = the 2948, but as=20 soon as I apply the õÅ;"t2948, as=20 you can see in the configuration, I can't communicate betweõÅ; tVLANs. Although the ACL is a "permit", all the traffic is blocked.</P> <P>Has anyone installed access-listsõÅ;thenvironment.</P> <P>I'll appreciate any help.</P> <P> </P> <P><BR>---<BR>Outgoing mail is certified ViruõÅ;eeanti-virus system (<A=20 href=3D"http://www.grisoft.com">http://www.grisoft.com>).<BR>Version: =õÅ;.2Virus Database: 135 - Release Date:=20 22/06/01</P></FONT></FONT></DIV></BODY></HTML>
------=_NextPart_001_0010_0ÑëÅ;AE
name="Gabriel Sanchez Jimenez.vcf" õÅ;enContent-Disposition: attachment; filename="Gabriel Sanchez Jimenez.vcf"
BEGIN:VCARõÅ;RSN:Sanchez Jimenez;Gabriel FN:Gabriel Sanchez Jimenez ORG:Servicom 2000;Ingenieria de Red TEL;WORK;VOICE:(34) 96332õÅ; TADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;;Primado Reig, 189, = Entresuelo=3D0D=3D0A;Valencia;;4602õÅ;aiEntresuelo=3D0D=3D0A=3D0D=3D0AValencia 46020=3D0D=3D0ASpain õÅ;WOEMAIL;PREF;INTERNET:gsanchez@servicom2000.com REV:20010712T125713Z END:VCARD
------=_NextPart_õÅ;00
From awalton@juniperõÅ; Received: from someone claiming to be alpha.jnpr.net (natint.juniper.net [207.17.136.129]) by õÅ;.n for <cisco-nsp@puck.nether.net>; Thu, 12 Jul 2001 09:33:09 -0400 (enõÅ;peReceived-Date: Thu, 12 Jul 2001 09:33:09 -0400 content-class: urn:content-classMIME-Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CX-MimeOLE: Produced By MicroõÅ; EDate: Thu, 12 Jul 2001 06:33:03 -0700 Message-ID: <C0D6C1C24CDBE1449BFEF1B72AFBF3A708A06E4A@postal.jnpõÅ;t>X-MS-TNEF-Correlator: Thread-Topic: unsubscribe Thread-Index: AcEK1yyqt1phkTqXTvinm/zWTgNwAQ== From: "õÅ;n To: <cisco-nsp@puck.nether.net> Subject: [nsp] unsubscribe
This is a multi-part message in õÅ; f
------_=_NextPart_001_01C10AD7.2D47C850 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: qõÅ;d-
unsubscribe
------_=_NextPart_001_01C10AD7.2D47C850 Content-Type: text/html; charset="us-ascii" Content-TraõÅ;r-
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-TyÑëÅ;CO6.0.4712.0"> <õÅ;E></HEAD> <BODY> <!-- Converted from text/rtf format -->
<P><FONT SIZE=3D2 FACE=3D"Arial">unsubscribe</õÅ;> <BR>
</BODY> </HTML> ------_=_NextPart_001_01C10AD7.2D47C850--
From KWortendyke@TimõÅ;dgReceived: from someone claiming to be toc1mail.Timebridge.com ([63.210.58.234]) by puckõÅ;he for <cisco-nsp@puck.nether.net>; Thu, 12 Jul 2001 11:01:46 -0400 (enveloõÅ;roReceived-Date: Thu, 12 Jul 2001 11:01:46 -0400 Received: by toc1mail.timebridge.com with IntõÅ;t id <3TSW6YMS>; Thu, 12 Jul 2001 11:01:35 -0400 Message-ID: <2FB8213C2B8AD411803F00D0B7741B0C6CõÅ;@tFrom: "Wortendyke, Ken" <KWortendyke@Timebridge.com> To: "'Gabriel Sanchez'" <gsanchez@servicom200õÅ;m>Subject: RE: [nsp] Access lists and uplink-redirect Date: TõÅ;12MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternatiõÅ; b
This message is in MIME format. Since your mail reader does not understanõÅ;is
------_=_NextPart_001_01C10AE3.889EB180 Content-Type: text/plainõÅ;ha
Gabriel, I haven't done much with ip uplink-redirect on a 2948LG-3, but... I think your ACL is blocõÅ; tSince the source and destination are behind the same interface, I believe you wouõÅ;eeand tweak it based on all your security concerns. interfaõÅ;igip access-group 101 in ! ! permit pings for reachability testing access-list 101 permit icmp any any echo aõÅ;s-! permit Telnet session from host 10 to host 2 access-list 101 permit tcp host 212õÅ;.7access-list 101 permit tcp host 212.101.75.2 host 212.101.75.10 established ! prevent comõÅ;ca212.101.75.0 subnets access-list 101 deny ip 212.101.75.0 0.0.0.255 2õÅ;01! permit communication to/from the Internet for any service access-list 101 permit ip any any ! Hope thiõÅ;lp Regards, Ken Wortendyke Internetworking Consultant Dimension Data 703-287-9698 (ofõÅ;) <mailto:Ken.Wortendyke@DiData.com> Ken.Wortendyke@DiData.com http://www.didata.com <http://www.did\15õÅ;co -----Original Message----- From: Gabriel Sanchez [mailto:gsanchez@servicom2000.com] Sent: Thursday, July 12, 2001 õÅ; ASubject: [nsp] Access lists and uplink-redirect
2 VLANs (Bridge-group 9 and 10)
*------õÅ;94
2948G-L3 config
....
ip uplink-redirect
bri
!
....
no ip address
no ip directed-broadcast
no cdp enable
bbridge-group 9 spanning-disabõÅ; !
interface FastEthernet7
no ip address
no ip directed-broadcast
no cdp enable
bridge-group 10
bridge-group 10 õÅ;ni
!
....
interface GigabitEthernet49
ip address 192.168.20.253 255.255.255.252
ip access-group telnet in
nõÅ; d
no cdp enable
!
....
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.20.254
!
......
ip access-lisõÅ;te
permit tcp host 212.101.75.10 host 212.101.75.2 eq telnet
As you can see in the previous config, I have to cõÅ;ni2948G-L3 working in an "uplink-redirect" environment with a 4908G-L3 as router.
All works fine; a piõÅ;oein the 4908G and return again to the other VLAN in the 2948, but as soon õÅ; asee in the configuration, I can't communicate betweõÅ;heAlthough the ACL is a "permit", all the traffic is blocked.
Has anyone installed access-lists in this kind ofõÅ;ir
I'll appreciate any help.
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system ( httpõÅ;ww<http://www.grisoft.com> ). Version: 6.0.263 / Virus Database: 135 - Release Date: 22/06/01
------_=_NextPaõÅ;01Content-Type: text/html; charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TransitionaõÅ;N"<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4134.õÅ; n<STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><SPAN class=731273013-12072001><FONT face=Arial color=#õÅ;ff<DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=2></FONT></õÅ;>&<DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=2>I haven't done much with ip uplink-õÅ;rebut...</FONT></SPAN></DIV> <DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=2><õÅ;T><DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=2>I think your ACL is blockinõÅ;e the source and destination are behind the same interface, I believe youõÅ;ldbased on all your security concerns.</FONTõÅ;PA<DIV><SPAN class=731273013-12072001></SPAN><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=731273õÅ;12class=731273013-12072001><FONT face=Arial color=#0000ff size=2></FONT></SPAN>&nõÅ;</<DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN clasÑëÅ;12<DIV><SPAN class=731ÑëÅ;13<DIV><SPAN class=731273013-120õÅ;1>size=2>!</FONT></SPAN></DIV> <DIV><SPAN class=731273013-12072001></SPAN><SPAN class=731273õÅ;12face=Arial color=#0000ff size=2>! permit pings for reachability testing</FONT></SPAN></DIV> <DIV><SPAN clasÑëÅ;12<DIV><SõÅ;clsize=2>access-list 101 permit icmp any any echo-reply</FONT></SPAN>õÅ;V>face=Arial color=#0000ff size=2>! permitõÅ;ne2</FONT></SPAN></DIV> <DIV><SPAN class=731273013-12072001><SPAN class=731273013-12072001><õÅ; host 212.101.75.2 eq telnet</FONT></SPAN></õÅ;><<DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=2>access-list 101 permit tcp host 212.101.7õÅ;hoestablished</FONT></SPAN></DIV> <DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=õÅ; p212.101.75.0 subnets</FONT></SPAN></DIV> <DIV><SPAN õÅ;s=size=2>access-list 101 deny ip 212.101.75.0 0.0.0.255 212.101.75.0 0.0õÅ;55<DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=2>! permit communication to/õÅ; t<DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff size=2õÅ;es<DIV><SPAN class=731273013-12072001><FONT face=Arial<DIV><SPAN class=731273013-12072001></SPAN><SPAN class<DIV><SPAN class=731273013-12072001><FONT face=AõÅ; cthis helps. </FONT></SPAN><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff sõÅ;2><DIV><SPAN class=731273013-12072001><FONT face=Arial color=#0000ff sizeõÅ;/F<DIV><SPAN class=731273013-12072001><FONT face=Arial><FONT color=#0000ff><FONT size=2>Regards, <BõÅ;n Data <BR>703-287-9698 (office) <BR>509-471-5338 (efax) <BR></FONTõÅ; hsize=2>Ken.Wortendyke@DiData.com</FONT></A><FONT size=2> <BR><SPAN claõÅ;31href="http://www.didata.com">http://www.didata.com></SPAN></FONT></FONT></FONT></DIV></SPAN> <DIV><õÅ; csize=2></FONT></SPAN> </DIV> <DIV><SPAN class=731273013-12072õÅ;<Fsize=2></FONT></SPAN> </DIV> <DIV class=OutlookMessageHeader dir=ltr align=left><FONT fõÅ;TasIze=2>-----Original Message-----<BR><B>From:</B> Gabriel Sanchez [mailto:gsanchez@servicom2000.comAM<BR><B>To:</B> cisco-nsp@puck.nether.net<BR><B>Suband uplink-redõÅ;t<<DIV><FONT face=Arial size=2><FONT color=#000000 size=2> <P>2 VLANs (Bridge-group 9 and 10)</P> <P>*-õÅ;--<P></P> <P>2948G-L3 config</P> <P>....</P> <P>ip uplinõÅ;di<P>bridge irb</P> <P>!</P> <P>....</P> <P>interface FastEthernet1</P> <P>no ip address</P> <P>no ip directed-broaõÅ;t<<P>No cdp enable</P> <P>bridge-group 9</P> <P>bridge-group 9 spanning-disabled</P> <P>!</P> <P>....</P> <P>interface FõÅ;th<P>no ip address</P> <P>no ip directed-broadcast</P> <P>no cdp enable</P> <P>bridge-group 10</P> <P>bridge-grouõÅ; s<P>!</P> <P>....</P> <P>interface GigabitEthernet49</P> <P>ip address 192.168.20.253 255.255.255.252<õÅ;<P<P>no ip directed-broadcast</P> <P>no cdp enable</P> <P>!</P> <P>....</P> <P>ip classless</õÅ;P><P>!</P> <P>......</P> <P>ip access-list extended telnet</P> <P>permit tcp hosõÅ;2.<P>As you can see in the previous config, I have to communicate two VLANs in a õÅ;G-</P> <P>All works fine; a ping goes from a VLANõÅ;thaddress in the 4908G and return again to the other VLAN in the 2948, but as soon as I&nbõÅ;ppyou can see in the configuration, I can't communicõÅ;beVLANs. Although the ACL is a "permit", all the traffic is blocked.</P> <P>Has anyone installed access-õÅ;s <P>I'll appreciate any help.</P> <P> </P> <P><BR>---<BR>Outgoing mail is certified VõÅ; Fanti-virus system (<A href="http://www.grisoft.com">http://www.grisoft.com>).<BR>Version: 6.0.õÅ;/ 22/06/01</P></FONT></FONT></DIV></BODY></HTML>
------_=_NextPart_001_01C10AE3.889EBõÅ;- Received: from someone claiming to be uk-cse-011.cisco.com (uk-cse-011.cisco.com [144.254.106.16]) by puck.nether.net (8.11.4/8.9.3) with ESMTP id f6CFIPA08868 for <cisco-nsp@puck.nether.net>; Thu, 12 Jul 2001 11:18:25 -0400 (envelope-from drajnovi@cisco.com) Received-Date: Thu, 12 Jul 2001 11:18:25 -0400 Received: (from drajnovi@localhost) by uk-cse-011.cisco.com (8.10.2+Sun/CA/950118) id f6CFI3N19788; Thu, 12 Jul 2001 16:18:03 +0100 (BST) Date: Thu, 12 Jul 2001 16:18:03 +0100 (BST) Message-Id: <200107121518.f6CFI3N19788@uk-cse-011.cisco.com> To: cisco-nsp@puck.nether.net From: Cisco Systems Product Security Incident Response Team <psirt@cisco.com> Sender: nobody@cisco.com Errors-To: nobody@cisco.com Reply-To: Cisco Systems Product Security Incident Response Team <psirt@cisco.com> Cc: psirt@cisco.com X-Mailer: GNU Emacs 19.34.1, VM 5.72 (beta) Subject: [nsp] Cisco Security Advisory: Cisco IOS PPTP Vulnerability
-----BEGIN PGP SIGNED MESSAGE-----
Cisco Security Advisory: Cisco IOS PPTP vulnerability Revision 1.0
For Public Release 2001 July 12 08:00 (UTC -0800) _________________________________________________________________ Summary
Point to Point Tunneling Protocol (PPTP) allows users to tunnel to an Internet Protocol (IP) network using a Point to Point Protocol (PPP). The protocol is described in RFC2637. PPTP implementation using Cisco IOS® software releases contains a vulnerability that will crash a router if it receives a malformed or crafted PPTP packet. No special conditions or router configuration is required. This vulnerability is present in all Cisco IOS releases that support PPTP protocol. PPTP is supported in the following software releases:
* 12.1 train, releases: T, E, EZ, YA, YD and YC * 12.2 train, all releases No other Cisco product is vulnerable. There is no workaround for this vulnerability. This advisory is available at http://www.cisco.com/warp/public/707/PPTP-vulnerability-pub.html Affected Products
This vulnerability is present in all Cisco IOS releases that are supporintg PPTP protocol. PPTP is supported in the following releases
* 11.x train does not supports PPTP * 12.1 train, releases: T, E, EZ, YA, YD and YC * 12.2 train, all releases To determine if a Cisco product is running an affected IOS, log in to the device and issue the command show version. Look for the "Internetwork Operating System Software" or "IOS (tm)" information, which also will have a version number. Other Cisco devices either will not have the command "show version" or will give different output. Details
By sending a crafted PPTP packet to a port 1723, a control PPTP port, it is possible to crash the router. This vulnerability does not require special router configuration. Enabling PPTP is sufficient to expose the vulnerability. The router will crash after it receives a single packet. This vulnerability is documented as Cisco Bug ID CSCdt46181 Impact
By repeaditly exploiting this vulnerability it is possible to cause permanent Denial of Service (DoS). This denial is not only of the PPTP functionality but the whole router will stop functioning. Software Versions and Fixes
Each row of the table describes a release train and the platforms or products for which it is intended. If a given release train is vulnerable, then the earliest possible releases that contain the fix and the anticipated date of availability for each are listed in the "Rebuild", "Interim", and "Maintenance" columns. A device running a release in the given train that is earlier the release in a specific column (less than the earliest fixed release) is known to be vulnerable. The release should be upgraded at least to the indicated release or a later version (greater than the earliest fixed release label). When selecting a release, keep in mind the following definitions: Maintenance Most heavily tested and highly recommended release of any label in a given row of the table. Rebuild Constructed from the previous maintenance or major release in the same train, it contains the fix for a specific defect. Although it receives less testing, it contains only the minimal changes necessary to effect the repair. Interim Built at regular intervals between maintenance releases and receive less testing. Interims should be selected only if there is no other suitable release that addresses the vulnerability, and interim images should be upgraded to the next available maintenance release as soon as possible. Interim releases are not available via manufacturing, and usually they are not available for customer download from CCO without prior arrangement with the Cisco TAC. In all cases, customers should exercise caution to be certain the devices to be upgraded contain sufficient memory and that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, contact the Cisco TAC for assistance as shown in the following section. More information on IOS release names and abbreviations is available at http://www.cisco.com/warp/public/620/1.html. +--------+-----------------------------------------------------------------+ | | Description of Image | | Train | or Platform Availability of Fixed Releases* | +--------+---------------------------+------------+----------+-------------+ | 12.1-based Releases | Rebuild |Interim** | Maintenance | +--------+---------------------------+------------+----------+-------------+ | 12.1E |Core/ISP support: GSR, | | | 12.1(8a)E | | |RSP, c7200 | | | | +--------+---------------------------+------------+----------+-------------+ | 12.1EZ |Early Deployment (ED): |12.1(6)EZ2 | | | | |special image | | | | +--------+---------------------------+------------+----------+-------------+ | |Early Deployment(ED): VPN, |Not Scheduled | | 12.1T |Distributed Director, +-------------------------------------+ | |various platforms |Upgrade recommended to 12.2(3) | +--------+---------------------------+------------+----------+-------------+ | | |Not Scheduled | | 12.1YA |Short-lived early +-------------------------------------+ | |deployment release |Upgrade recommended to 12.2(2)XB | +--------+---------------------------+------------+----------+-------------+ | 12.1YC |Short-lived early |12.1(5)YC1 | | | | |deployment release | | | | +--------+---------------------------+------------+----------+-------------+ | 12.1YD |Short-lived early |12.1(5)YD2 | | | | |deployment release |2001-June-25| | | +--------+---------------------------+------------+----------+-------------+ | 12.2-based Releases | Rebuild |Interim** | Maintenance | +--------+---------------------------+------------+----------+-------------+ | 12.2 |General deployment release | |12.2(1.1) |12.2(3) | | |for all platforms | | |2001-August | +--------+---------------------------+------------+----------+-------------+ | 12.2T |General deployment release | | |12.2(4)T | | |for all platforms | | | | +--------+---------------------------+------------+----------+-------------+ | 12.2XA |SPLOB | | |12.2(2)XA | +--------+---------------------------+------------+----------+-------------+ | 12.2XD |Short-lived early |12.2(1)XD1 | | | | |deployment release | | | | +--------+---------------------------+------------+----------+-------------+ | 12.2XE |Short-lived early | | |12.2(1)XE | | |deployment release | | | | +--------+---------------------------+------------+----------+-------------+ | 12.2XH |Short-lived early | | |12.2(1)XH | | |deployment release | | |2001-June-25 | +--------+---------------------------+------------+----------+-------------+ | 12.2XQ |Short-lived early | | |12.2(1)XQ | | |deployment release | | |2001-June-23 | +--------+---------------------------+------------+----------+-------------+ | Notes | +--------------------------------------------------------------------------+ | * All dates are estimated and subject to change. | | | | ** Interim releases are subjected to less rigorous testing than regular | | maintenance releases, and may have serious bugs. | +--------------------------------------------------------------------------+
Obtaining Fixed Software
Cisco is offering free software upgrades to eliminate this vulnerability for all affected customers. Customers with contracts should obtain upgraded software through their regular update channels. For most customers, this means that upgrades should be obtained through the Software Center on Cisco's Worldwide Web site at http://www.cisco.com. Customers whose Cisco products are provided or maintained through prior or existing agreement with third-party support organizations such as Cisco Partners, authorized resellers, or service providers should contact that support organization for assistance with the upgrade, which should be free of charge. Customers who purchase direct from Cisco but who do not hold a Cisco service contract and customers who purchase through third party vendors but are unsuccessful at obtaining fixed software through their point of sale should get their upgrades by contacting the Cisco Technical Assistance Center (TAC). TAC contacts are as follows:
* +1 800 553 2447 (toll-free from within North America) * +1 408 526 7209 (toll call from anywhere in the world) * e-mail: tac@cisco.com Please have your product serial number available and give the URL of this notice as evidence of your entitlement to a free upgrade. Free upgrades for non-contract customers must be requested through the TAC. Please do not contact either "psirt@cisco.com" or "security-alert@cisco.com" for software upgrades. Workarounds
There is no workaround for this vulnerability. Exploitation and Public Announcements
This vulnerability has been reported to us by a customer. The Cisco PSIRT received a report about potential exploitation of this vulnerability for malicious purpose against one customer. Status of This Notice: INTERIM
This is an interim security advisory. Cisco anticipates issuing updated versions of this notice at irregular intervals because there may be material changes in the facts. The reader is warned that this notice may contain inaccurate or incomplete information. Although Cisco cannot guarantee the accuracy of all statements in this notice, all of the facts have been checked to the best of our ability. Cisco anticipates issuing monthly updates of this notice until it reaches FINAL status. Note: A standalone copy or paraphrase of the text of this security advisory that omits the distribution URL in the following section is an uncontrolled copy and may lack important information or contain factual errors. Distribution
This notice will be posted on Cisco's Worldwide Web site at http://www.cisco.com/warp/public/707/PPTP-vulnerability-pub.html. In addition to Worldwide Web posting, a text version of this notice is clear-signed with the Cisco PSIRT PGP key and is posted to the following e-mail and Usenet news recipients:
* cust-security-announce@cisco.com * bugtraq@securityfocus.com * first-teams@first.org (includes CERT/CC) * cisco@spot.colorado.edu * comp.dcom.sys.cisco * firewalls@lists.gnac.com * Various internal Cisco mailing lists Future updates of this notice, if any, will be placed on Cisco's Worldwide Web server, but may or may not be actively announced on mailing lists or newsgroups. Users concerned about this problem are encouraged to check the URL given above for any updates. Revision History
Revision 1.0 2001-Jul-12 08:00 UTC -0800 Initial public release Cisco Security Procedures
Complete information on reporting security vulnerabilities in Cisco products, obtaining assistance with security incidents, and registering to receive security information from Cisco, is available on Cisco's Worldwide Web site at http://www.cisco.com/warp/public/707/sec_incident_response.shtml. This includes instructions for press inquiries regarding Cisco security notices. All Cisco Security Advisories are available at http://www.cisco.com/go/psirt _________________________________________________________________ This notice is Copyright 2001 by Cisco Systems, Inc. This notice may be redistributed freely after the release date given at the top of the text, provided that redistributed copies are complete and unmodified, and include all date and version information. _________________________________________________________________
-----BEGIN PGP SIGNATURE----- Version: 2.6.2
iQEVAwUBO028kWiN3BRdFxkbAQEgHAf+J+FhUoKCGi/L6h6KstLg6L5kOubaCfnW yBh0DYb/YWWRcHl2XGEYhiY66YXAyyrJiXKCoTW/g/eHGnnZLXvKpip+C5qQB/uT o7hQ+CGL8SrGq+j1adogDAaim4FfXLUGmD7N6/SOdeDi9nr8DNhyH9SrAouVvA1V syh/IwNy+8MTBvAlrbPgwoP6TLK6NC3Go1aruJyTvT955jZcPbIY2UNHwzl9TU0x uf9+jrWOfNho+02K4Yzz2BJSXy1XQ+Hk4fnQTC3g55FjyxrQZvhwhR1KC/fJp8kF o/aoOjgtSIVtSS9bjVxiNtz9t6aE6PLnvj3dNiORol6IWFKM8W/r3g== =6V7h -----END PGP SIGNATURE-----
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:44 EDT