Re: Static NATfrom inside to outside
- From: roberson@xxxxxxxxxxxx (Walter Roberson)
- Date: Thu, 16 Mar 2006 16:29:40 GMT
In article <1142505382.865719.315330@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
NETADMIN <chetan.kamra@xxxxxxxxx> wrote:
Does i have to do static NAT in this case
Please include enough of the context of previous discussions so that
people can figure out what is going on without having to refer back
to the previous messages. Merv is the only regular poster who uses
googlegroups extensively; for the rest of us, the previous messages
are -not- "right there" to be referred to. Indeed, in one of the
recent threads, two key posts in the thread never made it to the
news server I use, and as context was not sufficiently quoted I am
unable to be of assistance to them.
[PIX 6.3]
[internal server address is 192.168.whatever]
[simple request to forward http requests from the single public IP
to the internal server]
Does i have to do static NAT in this case
Yes, you need static NAT in order to allow new connections to
your internal server when it is not using a public IP internally.
[If it did happen to be using a public IP internally, then static
would still work fine, but there would also be one other command
that could be used instead.]
Just substitute that 192.168 address in to the 'static' command
that I showed
static (inside,outside) tcp interface http 192.168.x.x http
that together with the two other lines that I showed are all you
need for your situation.
.
- References:
- Static NATfrom inside to outside
- From: NETADMIN
- Re: Static NATfrom inside to outside
- From: Walter Roberson
- Re: Static NATfrom inside to outside
- From: NETADMIN
- Re: Static NATfrom inside to outside
- From: NETADMIN
- Static NATfrom inside to outside
- Prev by Date: 3620 session creation rate
- Next by Date: Re: 3620 session creation rate
- Previous by thread: Re: Static NATfrom inside to outside
- Next by thread: Routing question
- Index(es):
Relevant Pages
|
