Configuring access to server behind a SonicWall from WLAN zone to LAN using public IP address

08/17/2021 174 People found this article helpful 106,555 Views

Download

Print

Share

• LinkedIn
• Twitter
• Facebook
• Email
• Copy URL The link has been copied to clipboard

Description

This document describes how a host on a SonicWall WLAN can access a server on the LAN using the server's public IP address (typically provided by DNS).

EXAMPLE: 

NSA 4500 network in which the Primary LAN Subnet is 192.168.10.0 /24 and the Primary WAN IP is 1.1.1.1. Let's say you have a web site for your customers. You have already written the policies and rules needed so that outsiders can get to the web site, but it's really running on a private side server 192.168.10.20.

Now imagine that you are a person using a laptop on the private side of WLAN. You want to reach the server using its public name or public IP, because you do the same thing when your laptop is with you on the road.

If you sit on the private side and request http://www.domain.com, loopback is what makes it possible for that to work, even though the server is actually right next to you on a local IP address.

Resolution

�

Resolution for SonicOS 6.5

This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.

Creating Address Objects

1. Click Manage Tab.
2. Click Objects | Address Objects.
3. Click Add under Address Objects and create the address object for server on LAN.

• Address Object for server IP
  
  

  Name	My Server Private
  Zone	LAN
  Type	Host
  IP address	192.162.10.20

  

• Address Object for WAN(Public) IP
  
  

  Name	My Server Public
  Zone	WAN
  Type	Host
  IP address	1.1.1.1

  
  
  

Creating Loopback Policy.

1. Click Manage tab.
2. Click Rules | NAT Policies.
3. Click Add button and choose following settings.
   

   Original Source:Firewalled Subnets Translated Source:My Server Public Original Destination:Myserver Public Translated Destination:Myserver Private Original service:Any Translated Service:Original Inbound Interface:Any Outbound Interface:Any Comment:Loopback Policy Enable NAT Policy:Checked Create Reflexive Policy:Unchecked

Creating Firewall Access Rule.

1. Click Manage tab 
2. Click Rules | Access Rule.
3. Select view type from View Style and go to WLAN to LAN.
4. Click Add and choose the following settings.

Action:Allow From Zone:WLAN To Zone:LAN Source port:Any Service: Any Source: Any Destination: My Server Public Users Allowed:All Schedule:Always on Enable Logging:Checked Allow Fragmented Packets:Checked

Resolution for SonicOS 6.2 and Below

The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.

Creating Address Objects

1. Navigate to Network | Address Objects.
2. Click Add under address objects and create address object for server on LAN.

• Address Object for server IP
  

  Name	My Server Private
  Zone	LAN
  Type	Host
  IP address	192.162.10.20

  
  
  

• Address Object for WAN(Public) IP
  
  

  Name	My Server Public
  Zone	WAN
  Type	Host
  IP address	1.1.1.1

  
  
  

 Creating Loopback Policy.

1. Navigate to Network | NAT Policies.
2. Click Add button and choose following settings.
   
   

   Original Source:Firewalled Subnets Translated Source:My Server Public Original Destination:Myserver Public Translated Destination:Myserver Private Original service:Any Translated Service:Original Inbound Interface:Any Outbound Interface:Any Comment:Loopback Policy Enable NAT Policy:Checked Create Reflexive Policy:Unchecked

Creating Firewall Access Rule.

1. Navigate to Firewall | Access Rule.
2. Select view type from View Style and go to WLAN to LAN.
3. Click Add and choose the following settings.

Action:Allow From Zone:WLAN To Zone:LAN Source port:Any Service: Any Source: Any Destination: My Server Public Users Allowed:All Schedule:Always on Enable Logging:Checked Allow Fragmented Packets:Checked

Related Articles

• Parserror on Event logs.
• Switch from the Policy mode to classic mode on Gen 7 appliances
• Analyzing TCP reset(RST)packets

Categories

• Firewalls > TZ Series > Networking
• Firewalls > SonicWall SuperMassive 9000 Series > Networking
• Firewalls > NSa Series > Networking
• Firewalls > NSv Series > Networking