From: Robert DeVito (robertdevito@xxxxxxxxxxx)
Date: Sun Jan 28 2001 - 05:18:14 GMT-3
You could also use a secondary address.
192.168.12.0/24 private
123.123.123.0 /24 public
!
interface ethernet 0
ip address 123.123.123.1 255.255.255.0
ip address 192.168.12.1 255.255.255.0 secondary
ip nat inside
!
router ospf 1
network 123.123.123.0 0.0.0.255 area 0
!
Thoughts?
Robert
----Original Message Follows----
From: Troy Rader <troy@onenet.net>
Reply-To: Troy Rader <troy@onenet.net>
To: Atif Awan <atifawan@hotmail.com>
CC: ccielab@groupstudy.com
Subject: Re: Routing to NAT pool without static
Date: Sat, 27 Jan 2001 21:58:58 -0600 (CST)
Atif,
Thanks. That took care of it.
Troy
On Sun, 28 Jan 2001, Atif Awan wrote:
>
>
> Create a loopback with that public addressing space and do a controlled
> redistribute connected
>
>
> >From: Troy Rader <troy@onenet.net>
> >Reply-To: Troy Rader <troy@onenet.net>
> >To: ccielab@groupstudy.com
> >Subject: Routing to NAT pool without static
> >Date: Sat, 27 Jan 2001 20:38:35 -0600 (CST)
> >
> >-R1-------R2-------R3-
> >
> >R1 is running NAT. Private IP behind R1, public IP for the NAT pool. No
> >static routes allowed. OSPF is the routing protocol. How do I make R3
> >aware of the public IP in the NAT pool without a static?
> >
> >Hopefully this is not redundant. I searched the archives but found no
> >answer.
> >
> >Thanks.
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:45 GMT-3