<div>
Any device on the LAN side of the Sonicwall will have unrestricted access to go out the WAN by default, unless you specifically issue rules to prevent it.<br />
<br />
Is the problem that the contact is initiated from the WAN side, and you need to permit that?<br />
<br />
Please provide a little more info on what this device is and what you need to permit. For example, is it a process that initiates a download from the LAN, but the response is on another port or different service.
</div>


<div>
The device is a Cisco phone; the service is provided by another vendor and is being initiated from the WAN. &nbsp;The incoming port should not need to be translated, so I assume the any-&gt;any service designation would be fine (although insecure).
</div>


<div>
Are you trying to set up VOIP through the Sonicwall?
</div>


<div>
Yes, sorry, guess I should have started with that.
</div>


<div>
Does your switch the internal Cisco device connects to perform VLAN functions? My thought here is to create a VLAN, connect the VLAN'd port to a port on the sonicwall that is configured in transparent mode to the WAN. Your Cisco device could then take on a public IP address.<br />
<br />
It may seem scary to connect a port on your private switch to a public interface, but you'd be doing that anyway with a &quot;pass through&quot; solution. Which, by the way, I don't think the sonicwall will allow you to do. I think you're asking the sonicwall to suspend NAT and firewall functionality for a device that's connected to your private switch containing a public IP address. From your description, the vendor expects your Cisco device to have a public IP address. Using a VLAN would at least contain the traffic.
</div>


<div>
Also, you indicated another stipulation was that you could not run a wire special for this device. Your private switch has to connect to the sonicwall anyway, right?
</div>


<div>
<div class="content wysiwyg-content">
Here's the scenario. &nbsp;<br />
<br />
Usable Public IP range: &nbsp;0.0.0.2 - 0.0.0.5<br />
Sonicwall TZ190 in place, runs DHCP, hands out 172.16.233.100-200<br />
WAN interface of TZ190 is 0.0.0.2<br />
<br />
I have an internal device that has to utilize one of the public IP's (0.0.0.3). &nbsp;Re-cabling that device is not an option, the change must be made on the Sonicwall if possible. &nbsp;I need to have 0.0.0.3 pass through the TZ190 with no restrictions so the device can utilize it.<br />
<br />
Here's what I've tried (unsuccessfully):<br />
-Created WAN zone object with 0.0.0.3<br />
-Created LAN zone object with 0.0.0.3<br />
-Ran public server wizard these objects with the services set to &nbsp; Any-&gt;Any<br />
<br />
Firewall gurus, please point me in the correct direction.
</div>
</div>


Here's the scenario.  

Usable Public IP range:  0.0.0.2 - 0.0.0.5
Sonicwall TZ190 in place, runs DHCP, hands out 172.16.233.100-200
WAN interface of TZ190 is 0.0.0.2

I have an internal device that has to utilize one of the public IP's (0.0.0.3).  Re-cabling that device is not an option, the change must be made on the Sonicwall if possible.  I need to have 0.0.0.3 pass through the TZ190 with no restrictions so the device can utilize it.

Here's what I've tried (unsuccessfully):
-Created WAN zone object with 0.0.0.3
-Created LAN zone object with 0.0.0.3
-Ran public server wizard these objects with the services set to   Any->Any

Firewall gurus, please point me in the correct direction.

Allow a public IP to &quot;pass-through&quot; a Sonicwall TZ190

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.

Hardware Firewalls

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Allow a public IP to &quot;pass-through&quot; a Sonicwall TZ190

Allow a public IP to "pass-through" a Sonicwall TZ190