[c-nsp] NAT on one interface

Curtis Doty Curtis at GreenKey.net
Thu Aug 23 23:59:50 EDT 2007


Same thing with NVIs?

../C

Yesterday Rodney Dunn said:

> Bad idea because it causes process switching.
>
> Don't expect high throughput out of it.
>
> Rodney
>
>
> On Wed, Aug 22, 2007 at 03:40:55PM -0400, Joe Maimon wrote:
>> nat on a stick
>>
>> http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094430.shtml
>>
>> Church, Charles wrote:
>>
>>> Yeah, it's possible to policy route the traffic to a loopback that has
>>> nat inside configured on it, and then out the normal interface.  It's
>>> kludgy, but it'll work, I think.
>>>
>>>
>>> Chuck
>>>
>>> -----Original Message-----
>>> From: cisco-nsp-bounces at puck.nether.net
>>> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Michael Malitsky
>>> Sent: Wednesday, August 22, 2007 3:12 PM
>>> To: cisco-nsp at puck.nether.net
>>> Subject: [c-nsp] NAT on one interface
>>>
>>> Hello,
>>>
>>> I am trying to figure out if it's possible to configure NAT in IOS on
>>> just one interface.  Specifically, say I need to translate traffic flows
>>> between X.X.X.X and Y.Y.Y.Y.  Y.Y.Y.Y is reachable through one
>>> interface, that's my gateway to the "other" network.  However, X.X.X.X
>>> can be reached through multiple interfaces.  Normal NAT configuration
>>> requires me to specify a "nat inside" and a "nat outside" interfaces.  I
>>> can certainly specify the gateway interface to Y.Y.Y.Y as "nat outside",
>>> but I don't want to set a bunch of other interfaces as "nat inside" (nor
>>> do I want to involve them in NAT processing at all).  Is there any other
>>> way?
>>>
>>> Thanks,
>>> Michael Malitsky



More information about the cisco-nsp mailing list