4
Address Translation
85
The
required
IP
rule
is
defined
as
follows:
1. Change
the
current
CLI
context
to
be
the
main
IP
rule
set:
Device:/>
cc
IPRuleSet
main
2. Create
a
SAT
rule
for
the
translation:
Device:/IPRuleSet/main>
add
IPRule
Action=Allow
Service=http
SourceInterface=lan
SourceNetwork=lan_net
DestinationInterface=wan
DestinationNetwork=wan_ip
DestinationTranslation=SAT
SetDestinationAddress=Offset
NewDestinationIP4=our_server_ip
SourceTranslation=NAT
SetSourceAddress=AllToOne
NewSourceIP4=dmz_ip
3. Return
to
the
default
CLI
context
with
the
command:
Device:/IPRuleSet/main>
cc
Device:/>
Protocols not handled by SAT
SAT
can
deal
with
IP
‐
based
protocols
that
allow
address
translation
to
take
place.
However,
there
are
protocols
that
can
be
translated
only
in
special
cases,
and
some
protocols
that
cannot
be
translated
at
all.
Protocols
that
cannot
be
translated
using
SAT
usually
cannot
be
translated
using
NAT.
The
reasons
for
this
can
include:
•
The
protocol
requires
that
the
IP
addresses
are
cryptographically
unaltered.
This
applies
to
many
VPN
protocols.
•
The
protocol
embeds
its
IP
addresses
inside
TCP
or
UDP
level
data
and
requires
that
the
addresses
visible
at
the
IP
level
are
the
same
as
those
embedded
in
the
data.
Examples
include
FTP
and
NT
domain
logon
via
NetBIOS.
•
Either
party
is
attempting
to
open
new
dynamic
flows
to
the
addresses
that
are
visible
to
that
party.
In
some
cases,
this
can
be
resolved
by
modifying
the
application
or
the
SEG
configuration.
There
is
no
definitive
list
of
protocols
that
cannot
be
translated.
A
general
rule
is
that
VPN
protocols
and
protocols
that
open
secondary
flows
in
addition
to
the
initial
flow
can
be
difficult
to
translate.