• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

PAT and NAT

Red Squirrel

No Lifer
I've read on both. I know what NAT is and use it at home, well most other people do as well. But what makes PAT different? From what I read it just seems like its the same, exept PAT involves making port forwarding to different ports. So connecting to port 80 on the router outside may lead to an internal server on port 10000. But isin't this still a NAT? Just with port forwarding enabled? Or am I just missing something?
 
I'm sure my answer will get torn to shreds but what most people refer to as NAT is in actuality PAT. PAT will assign multiple inside IPs to one outside IP whereas NAT usually requires one outside IP for each inside IP.
 
NAT = network address translation. It works at layer3 regardless of layer4 (TCP/UDP port numbers)

PAT = port adress translation. It works at layer4

All SOHO gear uses PAT unless specifically told to do different.

So to your question - anytime source/destination addresses are changed by a device...that is technically port address translation. Network Address Translation only changes the******/dst layer3 IP addresses and doesn't change anything else.

It's mainly semantics however.
 
Yeah it's kind of misleading that people call soho routers "NAT routers", when it's really PAT they are using.
 
Back
Top