Open danderson opened 4 years ago
Not "overloading NAT" as in the RFCs, but port overloading as used by Palo Alto Networks, Juniper, Cisco et al.
Basically what they mean is "using one port for more than one client", by doing destination-dependent NAT mappings.
This should already be covered by address-and-port-dependent NAT behavior, but maybe the vendors do something fancier that needs special attention.
https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/port-overloading-factor-edit-security-nat-source-interface.html https://docs.paloaltonetworks.com/pan-os/7-1/pan-os-admin/networking/nat/dynamic-ip-and-port-nat-oversubscription
danderson
commented
4 years ago danderson
commented
4 years ago
Not "overloading NAT" as in the RFCs, but port overloading as used by Palo Alto Networks, Juniper, Cisco et al.
Basically what they mean is "using one port for more than one client", by doing destination-dependent NAT mappings.
This should already be covered by address-and-port-dependent NAT behavior, but maybe the vendors do something fancier that needs special attention.