Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Cisco Routing Issue
- Date: Tue, 27 May 2003 10:28:59 -0400
- From: Josh Glover <jmglov@example.com>
- Subject: Re: [tlug] Cisco Routing Issue
- References: <20030527141659.GB19936@example.com>
- User-agent: Mutt/1.4.1i
Quoth Josh Glover (Tue 2003-05-27 10:16:59AM -0400): > I am putting a Linux firewall in behind our Cisco router: > > > INTERNET == ISP == 123.456.7.27 > | > ROUTER > | > 123.456.1.1 == 123.456.1.2 > | > FIREWALL > | > 123.456.1.3 == 123.456.1.0/24 > > > What I need to do is configure the router to use FIREWALL (the Linux box) as > the next hop for all packets destined for 123.456.789.0/24. Did a little more digging, and I may have answered my own question. However, I want to be affirmed by a card-carrying Cisco admin before I go (potentially) sodding my router up. Do I need to do something like: ip nhrp nhs 123.456.1.3 123.456.1.0 255.255.255.0 in privileged exec mode? I want 123.456.1.3 to be a static next hop, since it will not be running any sort of routing protocol. Am I on the right track? -- Josh Glover <jmglov@example.com> Associate Systems Administrator INCOGEN, Inc. http://www.incogen.com/ GPG keyID 0x62386967 (7479 1A7A 46E6 041D 67AE 2546 A867 DBB1 6238 6967) gpg --keyserver pgp.mit.edu --recv-keys 62386967Attachment: pgp00115.pgp
Description: PGP signature
- Follow-Ups:
- Re: [tlug] Cisco Routing Issue
- From: Matt Doughty
- References:
- [tlug] Cisco Routing Issue
- From: Josh Glover
Home | Main Index | Thread Index
- Prev by Date: [tlug] Cisco Routing Issue
- Next by Date: Re: [tlug] Gentoo Linux Kernel Compile Trouble
- Previous by thread: [tlug] Cisco Routing Issue
- Next by thread: Re: [tlug] Cisco Routing Issue
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links