In this scenario, Company A wants all users on the private network to be able to access the Internet without registered IP addresses. Company A also wants to make the SMTP and Web servers on the intranet available to public clients. Company A has the following requirements:
Configure a Novell BorderManager server with NAT in dynamic mode to allow private users to access the Internet
Make private SMTP and Web servers available through NAT static mode
Consider filter settings for SMTP and Web servers on the NAT interface
The following Novell BorderManager components are used to implement this scenario, as shown in Figure 6-6:
Packet filtering
NAT
NOTE:This scenario might not apply if your intranet Web server has links to other intranet Web servers, or if your intranet SMTP server has links to other intranet SMTP servers.
Figure 6-6 Using Novell Novell BorderManager as an Address Translator
To use Novell BorderManager as an address translator, Company A must perform the following general sequence of steps:
Install Novell BorderManager, enabling packet filtering on public interfaces.
For more information and Novell BorderManager installation procedures, see Novell BorderManager 3.9 Installation Guide .
Enable the following filters:
For the intranet SMTP server, insert filter exceptions on the NAT interface to allow inbound SMTP requests and outbound SMTP responses.
For the intranet Web server, insert filter exceptions on the NAT interface to allow inbound HTTP requests and outbound HTTP responses.
Enable and configure NAT to use dynamic and static mode.
For more information on configuration procedures, see Novell BorderManager 3.9 Administration Guide .