Article View: comp.dcom.sys.cisco
Article #2307Re: Pix and Router
From: findo
Date: Tue, 02 Oct 2001 03:41
Date: Tue, 02 Oct 2001 03:41
53 lines
3118 bytes
3118 bytes
Thousands Thx. But I have one question. I can see the PIX is the member of the subnet address ? Is it for example my router have ip 192.168.0.1/255.255.255.240 then the Pix also in this subnet without config anythings in PIX? "S. Gione" <sgione@hotmail.com> ????? news:e7543808.0110011724.169e1dea@posting.google.com... > Findo; > > The normal method by which a PIX is connected to a router is to simply > connect it to the same Ethernet segment ... switch, hub, or cross-over > cable. > > The caveat is that the outside IP address of the PIX *MUST* be in the > same network/subnet as the Router Ethernet interface. You do not need > to use any routing protocols. > > If you are looking at the router's routing tables, you should not see > the PIX IP address. What you should see is the Network/subnet > address, of which the PIX is a member. > > > "findo" <findo@netvigator.com> wrote in message news:<9p8sut$riu4@imsp212.netvigator.com>... > > Dear, > > > > Then can you show me the RIP command that can make the PIX connect to the > > Router? > > Just give me an example is ok and enough. Thx > > "Walter Roberson" <roberson@ibd.nrc.ca> ���g��l�� > > news:9p84o3$mgv$1@canopus.cc.umanitoba.ca... > > > In article <9p3b8f$a8p42@imsp212.netvigator.com>, > > > findo <findo@netvigator.com> wrote: > > > :I connect the pix to the (2500) router, but the router's routing table > > can't > > > :see the pix port address? How can I solve it by changing some of the SW > > > :parameter. > > > > > :Please help with giving approximate command in router and PIX > > > > > > You are not giving us a lot to work on. How have you configured > > > the two systems? > > > > > > Keep in mind that the PIX does not send out any routing information > > > by default, so if you are expecting the 2600 to learn the route > > > to the PIX, you will have to configure RIP on both ends. > > > > > > If you are not expecting the 2600 to learn the route from the PIX, then > > > any routing problem is entirely on the 2600.
Technical Details
Message-ID:
<9pbcpb$jpb2@imsp212.netvigator.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsgate.netvigator.com!imsp212.netvigator.com!not-for-mailReferences:
<9p3b8f$a8p42@imsp212.netvigator.com> <9p84o3$mgv$1@canopus.cc.umanitoba.ca> <9p8sut$riu4@imsp212.netvigator.com> <e7543808.0110011724.169e1dea@posting.google.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII X-Google-Thread: 102702,c5e866f9cbe37a74 X-Google-Attributes: gid102702,public X-Google-Thread: 101522,c5e866f9cbe37a74 X-Google-Attributes: gid101522,public X-Google-ArrivalTime: 2001-10-01 20:40:04 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsgate.netvigator.com!imsp212.netvigator.com!not-for-mail From: "findo" <findo@netvigator.com> Newsgroups: comp.dcom.sys.cisco,it.comp.reti.cisco Subject: Re: Pix and Router Date: Tue, 2 Oct 2001 11:41:02 +0800 Organization: IMS Netvigator Lines: 55 Message-ID: <9pbcpb$jpb2@imsp212.netvigator.com> References: <9p3b8f$a8p42@imsp212.netvigator.com> <9p84o3$mgv$1@canopus.cc.umanitoba.ca> <9p8sut$riu4@imsp212.netvigator.com> <e7543808.0110011724.169e1dea@posting.google.com> NNTP-Posting-Host: pcd162247.netvigator.com X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2462.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000