Cisco Cisco Packet Data Gateway (PDG) Nota Di Rilascio
NAT Changes in Release 15.0
▀ NAT Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
360
NAT Enhancements for September 30, 2013
NAT Feature Changes as of September 30, 2013
This section provides information on NAT feature changes in release 15.0.
Important:
For more information regarding features in this section, refer to the Network Address Translation
Administration Guide for this release.
New NAT Features
This section identifies new NAT features available in release 15.0.
SIP ALG Support for NAT64
SIP ALG is supported for NAT64 in this release. SIP packets can now undergo NAT64 translation.
SIP request and response packets contain IP addresses embedded in their headers. For SIP packets originating from an
IPv6 network, the IP addresses will be in IPv6 format. The destination IPv4 network will not be able to process the SIP
packets if these IPv6 addresses are not translated to their corresponding IPv4 addresses. Similarly the IPv4 addresses
coming from IPv4 network need to be converted to their corresponding IPv6 addresses. With this release, SIP ALG
interworks with NAT to perform these translations so that SIP packet processing is unaffected at both IPv6 and IPv4.
IPv6 network, the IP addresses will be in IPv6 format. The destination IPv4 network will not be able to process the SIP
packets if these IPv6 addresses are not translated to their corresponding IPv4 addresses. Similarly the IPv4 addresses
coming from IPv4 network need to be converted to their corresponding IPv6 addresses. With this release, SIP ALG
interworks with NAT to perform these translations so that SIP packet processing is unaffected at both IPv6 and IPv4.
Server IP Address in Access Rule Definitions
Access Rule Definitions now support Server IP address to avoid configuring multiple rule options as part of Firewall
rules. With this release, the
rules. With this release, the
is specified as the server IP address, this address in the uplink direction will be treated as the destination address, and in
downlink direction will be treated as the source address.
downlink direction will be treated as the source address.
Modified NAT Features
This section identifies NAT features modified in release 15.0.
Enabling NAT
Previous Behavior: NAT will be disabled by default if the assigned IP is already a public IP.
New Behavior: A new keyword
skip-nat-subscriber-ip-check
is added in this release. On enabling this option,
the private IP check for the corresponding non-NAT pool will be skipped, while NAT will be enabled (if configured) for
this pool although it is a public pool. The user can control enabling of NAT irrespective of whether the assigned IP is a
private or public IP address. Refer to the
this pool although it is a public pool. The user can control enabling of NAT irrespective of whether the assigned IP is a
private or public IP address. Refer to the
NAT Busyout
When a NAT pool is busied out, no new calls will receive IP from the busied out pool. Only calls which have received
IP from the pool prior to busy out will be using the IP. Busyout feature is now supported for both NAT and ordinary
pools.
IP from the pool prior to busy out will be using the IP. Busyout feature is now supported for both NAT and ordinary
pools.