<div>
<div class="content wysiwyg-content">
I am looking for some advice on configuring my new Sonicwall TZ215. <br />
<br />
We have a network with 3 VLANs. The first two VLANs use the primary WAN as configured on the Sonicwall. I have an extra IP and was wondering about using it as a public facing (but still firewalled) address for VLAN 3. The two WAN IPs are in the same subnet, and are accessible via the same router.<br />
<br />
Since I have a physical connection to the router on WAN (X1) can I utilize that? Do I need to use one of the other X interfaces on the Sonicwall configured as WAN? I'm trying to host a few services logically separated from our primary two networks and am unsure how to proceed.<br />
<br />
Advice on the logic, rules, and routing would be greatly appreciated.<br />
<br />
Thank you!
</div>
</div>


I am looking for some advice on configuring my new Sonicwall TZ215. 

We have a network with 3 VLANs. The first two VLANs use the primary WAN as configured on the Sonicwall. I have an extra IP and was wondering about using it as a public facing (but still firewalled) address for VLAN 3. The two WAN IPs are in the same subnet, and are accessible via the same router.

Since I have a physical connection to the router on WAN (X1) can I utilize that? Do I need to use one of the other X interfaces on the Sonicwall configured as WAN? I'm trying to host a few services logically separated from our primary two networks and am unsure how to proceed.

Advice on the logic, rules, and routing would be greatly appreciated.

Thank you!

Multiple VLANs and multiple WAN addresses on Sonicwall TZ 215

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

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.