IP Address Aliasing

The Internet routes messages based on the destination IP Address, not the source address or the type of data. That means that your Web fetches and your FTP traffic follow the same path through the network, whether you want them to or not. If this is a problem, and it has been for some of our customers, we can help. We set up a NAT to provide IP Address conversion without regard for the service, and create "aliases" for actual IP Addresses.

Customer Case Study

One of our customers had the following problem. They had two offices in Europe, each with its own IP Network, and each connected by the same ISP. In addition, there were two dedicated links from that European ISP into their main site in the US. They wanted traffic from one site (mostly bulk data transport and timesharing) to stay separate from traffic from the other site (high-speed client/server transaction processing data). The big problem was, both of these connections went to the very same set of machines in their main site.

We installed a NAT and created a new set of IP Addresses for these machines. Now, one European office would use the real addresses, and the other would use the new addresses. The host computers at the main site were configured to route messages to the second site via the NAT, and the problem was solved. Other than the static route to the NAT, nothing was changed on the many hosts that were involved. We call this re-mapping mode Fixed Mapping Mode, and it is available in all of our products.

This page was last modified on April 19, 1996.

This information is proprietary to Network Safety. Network Safety, WebElite and NetNAT are trademarks of Network Safety. For information on our products and services, please contact our sales department. This page was prepared using WebElite, our professional editor for the Web.