ProSafe VPN Firewall 200 FVX538 Reference Manual
4-6
Firewall Protection and Content Filtering
v1.0, March 2009
Inbound Rules (Port Forwarding)
Because the FVX538 uses Network Address Translation (NAT), your network presents only one
IP address to the Internet and outside users cannot directly address any of your local computers.
However, by defining an inbound rule you can make a local server (for example, a Web server or
game server) visible and available to the Internet. The rule tells the firewall to direct inbound
traffic for a particular service to one local server based on the destination port number. This is also
known as port forwarding.
Whether or not DHCP is enabled, how the PCs will access the server’s LAN address impacts the
Inbound Rules. For example:
•
If your external IP address is assigned dynamically by your ISP (DHCP enabled), the IP
address may change periodically as the DHCP lease expires. Consider using
Dyamic DNS
(under Network Configuration) so that external users can always find your network (see
“Configuring Dynamic DNS (If Needed)” on page 2-14
.
•
If the IP address of the local server PC is assigned by DHCP, it may change when the PC is
rebooted. To avoid this, use the Reserved IP address feature in the
LAN Groups
menu (under
Network Configuration) to keep the PC’s IP address constant (see
“Setting Up Address
Reservation” on page 3-9
.
Bandwidth Profile
Bandwidth Limiting determines the way in which the data is sent to/from your host.
The purpose of bandwidth limiting is to provide a solution for limiting the outgoing/
incoming traffic, thus preventing the LAN users for consuming all the bandwidth of
our internet link. Bandwidth Limiting for outbound traffic will be done on the available
WAN interface in the single port and Auto-Failover modes. The limiting will be done
on the user-specified interface in Load Balancing mode. The bandwidth limiting for
inbound traffic will be done on the LAN interface for all WAN modes. Bandwidth
Limiting will not apply to the DMZ interface.
Log
This determines whether packets covered by this rule are logged. Select the desired
action:
•
Always – always log traffic considered by this rule, whether it matches or not. This
is useful when debugging your rules.
•
Never – never log traffic considered by this rule, whether it matches or not.
Table 4-2.
Outbound Rules (continued)
Item
Description