Cisco Cisco Packet Data Gateway (PDG)
ePDG Changes in Release 16
▀ ePDG Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
140
clear subscribers tx-data value epdg-service epdg_service_name
clear subscribers username value epdg-service epdg_service_name
CSCuj21726 - Sessmgr changes for SWu over IPv6 transport support
Feature Changes
SWu over IPv6 transport support
With this release, ePDG supports IPv6 from the UEs during the IPsec negotiation. When a UE attaches to a WiFi AP,
the WiFi Access Point may assign the UE an IPv6 address. Once the UE is provided an IPv6 address the UE will be
directed to establish an IPSec connection to the ePDG.
the WiFi Access Point may assign the UE an IPv6 address. Once the UE is provided an IPv6 address the UE will be
directed to establish an IPSec connection to the ePDG.
Previous Behavior: Only IPv4 bind address was allowed under ePDG Service.
New Behavior: Both IPv4 and IPv6 address can be bind simultaneously under ePDG Service.
Customer Impact: No.
bind address
ePDG supports IPv6 bind address.
bind address bind_address crypto-template crypto_template_service_name
CSCul15285 - Local PGW resolution required for ePDG
Feature Changes
Local PGW resolution required for ePDG
Previous Behavior: The local PGW resolution is not available.
New Behavior: The local PGW resolution is supported with apn-profile, operator-policy and subscriber-map.
Customer Impact: No.
apn-profile
ePDG-service supports local PGW resolution.
ePDG is enabled to configure pgw address.
apn-profile profile_name pgw address address
ePDG is enabled to link apn-profile with apn-ni.
operator-policy name name
ePDG is enabled to link operator-policy with subscriber-map.