Ok, give me the whole scenario. I still do not understand what the
underlying goal here is.
Start with the problem you are trying to solve and what you have tried thus
far as far as solutions.
-Patrick
>>> "Leigh Anne Chisholm" 08/23/01 12:42PM >>>
Okay, let's say I have a switch. Then how would that change things? You
can't specify ISL encapsulation on a subinterface on an Ethernet interface.
You can't assign an IP address on an Ethenet subinterface either because you
get that darned message, "Configuring IP routing on a LAN subinterface is
only allowed if that subinterface is already configured as part of an IEEE
802.10, IEEE 802.1Q, or ISL vLAN." There is no encapsulation command
available for an Ethernet interface in interface configuration mode.
Someone suggested configuring the outside translated address on a loopback
interface. I don't know if this will or won't work because I'm just not
familiar enough with NAT and I'm behind on a project so I really don't have
time to learn the ins and outs and look for a solution myself. I was hoping
someone else had been down this road and could help out.
-- Leigh Anne
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Peter Slow
Sent: Thursday, August 23, 2001 9:20 AM
To: [EMAIL PROTECTED]
Subject: RE: NAT using a single interface [7:16902]
yeah, but you need to use sub interfaces. yah cant do it with a single
interface regardless of wether it will work theoretically, because IOS needs
the ip nat inside/outside commands, and wont let you put them on and
interface at the same time
Unfortunately, this means that you need a switch, because cisco wont allow
you to config inet addresses on a subif if you have no encap spec'd.
Personally i think it'd be cake to get nat up and running on the same
interface if they diddnt require you to config an encap.
-Peter
-----Original Message-----
From: Patrick Ramsey [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 23, 2001 10:16 AM
To: [EMAIL PROTECTED]
Subject: Re: NAT using a single interface [7:16902]
well I am not sure to what application this would be usefull for, but if IOS
supported this funtionallity, you would have to create sub interfaces with
different ip addresses on different networks. then set your inside
interface to one sub and the outside interface to the other sub just as you
would on a normal router.
But I have to ask... If you have 2 subnets on the same network, in theory
you would have a lot of machines on each of those subnets trying to talk to
one another. Is this correct? Why not just use that ethernet port as a one
armed router? (I would then assume that you are migrating your network from
one subnet to another) so this would not be a permanent intallation. (as
this is very unefficient)
If this is not the case, please explain your situation... I'm interested in
the need for this scenario.
-Patrick
>>> "Leigh Anne Chisholm" 08/22/01 06:27PM >>>
I've searched the Groupstudy archives... there's been much speculation as
to whether or not this can be done. Has anyone managed to get NAT using a
single Ethernet interface to work?
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=17004&t=16902
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
