New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Port overloading behavior #2

Open

danderson opened this issue Jan 14, 2020 · 1 comment

Owner

danderson commented Jan 14, 2020

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.

Owner Author

danderson commented Jan 14, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment