Age | Commit message (Collapse) | Author | Files | Lines |
|
Nat api in VPP (https://wiki.fd.io/view/VPP/SNAT#API_3)
uses different api calls for nat44 and nat64.
While ietf-nat model allows to distinguish between
static nat44 and nat64 mappings,
external-ip-address-pool needs to be augmented
with nat pool type.
Change-Id: I2ce1fa3a8241c337c617bcbb77ec5eb2a33044e4
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
|
|
Change-Id: I009d790e21ff5019f94145e1aa1e08f87b6729ca
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
|
|
Also order of revisions was sorted starting from most current.
Change-Id: I21fd35cfdb1cc5601b3fb40c9f3755bd3b995b14
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
|
|
Change-Id: I2a38b72f43e61f7fc9a11d0e908996d284e96026
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
|
|
Change-Id: I249b34a42b7e9c9a38fbef9d268c658943000394
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
|
|
Reflects SNAT from VPP:
- 1:1 Static IPv4 mapping
- interface in/out NAT feature management
Bonus:
- Support presence containers in infra
Change-Id: Ieb38526f83edbae5e605d5c7e39bb22bbafc50e5
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
|