![](/images/new-backgrounds/1118988/118988449x1.webp)
Understanding Netopia NAT Behavior C-5
Now both IP packets have the exact same source IP address (200.1.1.40) and source ports (400). The Netopia R7200 is then able to distinguish between the two IP packets by changing the source TCP or UDP ports and keeping this information in an internal table. As seen above, the source port for Workstation A has been changed to 5001 and the source port for Workstation B has been changed to 5002.
If you were to look at the internal port mapping table that is maintained by the Netopia R7200, it would look similar to the following:
Source LAN IP | Source LAN Port | Remapped LAN Port | ||
192.168.5.2 | TCP | 400 | TCP | 5001 |
192.168.5.3 | TCP | 400 | TCP | 5002 |
With this information the Netopia R7200 can determine the appropriate routing for an IP response from the Internet. In this case, when the WWW server responds with a destination port of 5001, the Netopia R7200 can see that this packet's destination on the local LAN interface is actually Workstation A at IP address 192.168.5.2. Likewise, with the response for port 5002, the Netopia R7200 can see that this packet's destination on the local LAN interface is actually Workstation B at IP address 192.168.5.3.
Exported services
Note that this “automatic” port remapping and IP address substitution only works in one direction – for IP packets that originated on the LAN interface destined to the WAN interface and the Internet. In order for port remapping and IP address substitution to work in the other direction – that is, hosts on the Internet that want to originate an IP packet destined to a host on the Netopia R7200s LAN interface – a manual redirection of TCP or UDP ports as well as destination IP addresses within the Netopia R7200 is required. This manual port remapping and IP address substitution is accomplished by setting up exported services.
Exported services are essentially
For example, suppose the WWW server on the Internet with the IP address of 163.176.4.32 wants to access Workstation B on the Netopia R7200s local LAN interface which is operating as an FTP server. The IP address for Workstation B is 192.168.5.3, which is not a valid IP address, and thus the WWW server on the Internet cannot use this IP address to access Workstation B.
The WWW server on the Internet would then have to use the single valid IP address that was acquired on the Netopia R7200's WAN interface to access any host on the Netopia R7200's local LAN interface, since this is the only valid address for the Internet. But if the WWW server on the Internet opens a connection to 200.1.1.40 via port 21 (FTP) and no exported services are defined on the Netopia R7200, the Netopia R7200 will discard the incoming packet since the Netopia R7200 itself does not perform the requested service.
You can see why exported services are necessary. In the example above, an exported service needs to be defined within the Netopia R7200 redirecting any incoming IP traffic with a destination port of 21 to the host on the local LAN interface with the IP address of 192.168.5.3.