ip nat {in | out}
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
583
Alcatel-Lucent
Beta
Beta
OmniAccess 700 CLI Command Reference Guide
IP
NAT
{
IN
|
OUT
}
ip nat
{
in
|
out
} <
nat policy-name
>
D
ESCRIPTION
Enter this command in the Interface Configuration mode. This command is used
to attach a NAT policy to an interface in ‘in’ or ‘out’ direction.
P
ARAMETERS
Note:
Each interface can have only one ingress and one egress NAT policy.
E
XAMPLE
In the example below, HTTP requests initiated from internal network will be
translated and sent to external network. Returning HTTP responses are
automatically allowed and translated even if there is a filter to block:
ALU(config)# match-list m1
ALU(config-match-list m1)# ip any any type ftp
ALU(config)# exit
ALU(config)# ip filter f1
ALU(config-filter f1)# match m1 deny
ALU(config)# exit
ALU(config)# ip nat n1
ALU(config-nat n1)# match m1 source-nat
ALU(config)# exit
ALU(config)# interface GigabitEthernet 7/0
ALU(config-if GigabitEthernet7/0)# ip filter in f1
ALU(config-if GigabitEthernet7/0)# ip nat out n1
Parameter
Description
in
The keyword "in" signifies that ingress traffic is subjected to
the NAT, only if all classifiers in this NAT object are
matched.
out
The keyword "out" denotes that egress traffic is subjected to
the NAT, if all classifiers in this NAT object are matched.
nat policy name
Name of the NAT policy.
