02-23-2013, 04:47 PM
I think you are getting NAT/PAT confused with DHCP
DHCP assigns IP addresses from a pool of pre-defined DHCP addresses for a time (set by the admin).
PAT (Port address Translation) is a form of PAT but not exactly the same, in the same way that dog is a type of animal but animal is not a type of dog. NAT covers a wider scope.
So, concentrating on PAT only, an outgoing packet looking for a web page would be looked at by the router as "private ip: IE session", with the private IP address then being stored in the PAT table and the PAT table having an entry with "router IP:80 is translated to private IP:IE session.......the router then knows then when it comes back from the web server looking for "router IP:80 - it can easily be translated back to the private IP address because it has the entry.
The answer is therefore the one stated
Hope that helps
DHCP assigns IP addresses from a pool of pre-defined DHCP addresses for a time (set by the admin).
PAT (Port address Translation) is a form of PAT but not exactly the same, in the same way that dog is a type of animal but animal is not a type of dog. NAT covers a wider scope.
So, concentrating on PAT only, an outgoing packet looking for a web page would be looked at by the router as "private ip: IE session", with the private IP address then being stored in the PAT table and the PAT table having an entry with "router IP:80 is translated to private IP:IE session.......the router then knows then when it comes back from the web server looking for "router IP:80 - it can easily be translated back to the private IP address because it has the entry.
The answer is therefore the one stated
Hope that helps