SonicWALL Internet Security Appliances Manual Do Utilizador
Page 188 SonicWALL Internet Security Appliance Administrator’s Guide
Require authentication of local users
Selecting this check box requires that all outbound VPN traffic on this SA is from an authenticated
user. Unauthenticated traffic is not allowed on the VPN tunnel.
user. Unauthenticated traffic is not allowed on the VPN tunnel.
Require authentication of remote users
Enabling this feature requires that all inbound traffic on this SA is from an authenticated user.
Unauthenticated traffic is not allowed on the VPN tunnel. Select Remote users behind VPN gateway
if remote users have a VPN tunnel terminating on the VPN gateway. Select Remote VPN clients
behind VPN gateway if remote users require authentication using XAUTH and are accessing the
SonicWALL via a VPN client.
Unauthenticated traffic is not allowed on the VPN tunnel. Select Remote users behind VPN gateway
if remote users have a VPN tunnel terminating on the VPN gateway. Select Remote VPN clients
behind VPN gateway if remote users require authentication using XAUTH and are accessing the
SonicWALL via a VPN client.
Enable Windows Networking (NetBIOS) broadcast
Computers running Microsoft Windows
®
communicate with one another through NetBIOS broadcast
packets. Select the Enable Windows Networking (NetBIOS) broadcast check box to access remote
network resources by browsing the Windows
network resources by browsing the Windows
®
Network Neighborhood.
Apply NAT and firewall rules
This feature allows a remote site’s LAN subnet to be hidden from the corporate site, and is most
useful when a remote office’s network traffic is initiated to the corporate office. The IPSec tunnel is
located between the SonicWALL WAN interface and the LAN segment of the corporation. To protect
the traffic, NAT (Network Address Translation) is performed on the outbound packet before it is sent
through the tunnel, and in turn, NAT is performed on inbound packets when they are received. By
using NAT for a VPN connection, computers on the remote LAN are viewed as one address (the
SonicWALL public address) from the corporate LAN.
If the SonicWALL uses the Standard network configuration, using this check box applies the firewall
access rules and checks for attacks, but not NAT.
Alert You cannot use this feature if you have Route all internet traffic through this SA enabled.
Alert Offices can have overlapping LAN IP ranges if the Apply NAT and firewall rules option is
selected.
useful when a remote office’s network traffic is initiated to the corporate office. The IPSec tunnel is
located between the SonicWALL WAN interface and the LAN segment of the corporation. To protect
the traffic, NAT (Network Address Translation) is performed on the outbound packet before it is sent
through the tunnel, and in turn, NAT is performed on inbound packets when they are received. By
using NAT for a VPN connection, computers on the remote LAN are viewed as one address (the
SonicWALL public address) from the corporate LAN.
If the SonicWALL uses the Standard network configuration, using this check box applies the firewall
access rules and checks for attacks, but not NAT.
Alert You cannot use this feature if you have Route all internet traffic through this SA enabled.
Alert Offices can have overlapping LAN IP ranges if the Apply NAT and firewall rules option is
selected.
Forward Packets to Remote VPNs
Selecting the Forward Packets to Remote VPNs check box for a Security Association allows the
remote VPN tunnel to participate in the SonicWALL routing table. Inbound traffic is decrypted and
can now be forwarded to a remote site via another VPN tunnel. Normally, inbound traffic is
decrypted and only forwarded to the SonicWALL LAN or a specific route on the LAN specified on the
Routes tab located under the Advanced section.
Enabling this feature allows a network administrator to create a “hub and spoke” network
configuration by forwarding inbound traffic to a remote site via a VPN security association. To create
a “hub and spoke” network, enable the Forward Packets to Remote VPNs check box for each
remote VPN tunnel to participate in the SonicWALL routing table. Inbound traffic is decrypted and
can now be forwarded to a remote site via another VPN tunnel. Normally, inbound traffic is
decrypted and only forwarded to the SonicWALL LAN or a specific route on the LAN specified on the
Routes tab located under the Advanced section.
Enabling this feature allows a network administrator to create a “hub and spoke” network
configuration by forwarding inbound traffic to a remote site via a VPN security association. To create
a “hub and spoke” network, enable the Forward Packets to Remote VPNs check box for each