Legacy-undetected port map conflicts
Status: Beta
Brought to you by:
jsulliva
It is possible to add a Resource Override with a port map (NAT using a PEP public IP address) on a service used by the PEP. That should not be allowed since they will try to use the same public IP address for the same service. Likewise, it is possible to add a Service to a PEP which is already being used by a port mapping Resource Override.
Have added detecting and resolving conflicts with Port Maps when adding a PEP Resource but have not done the reverse nor added logic to return NAT fragments when the PEP Resource is deleted or edited.