There may be several network segments in your organization to segregate user workstations from public webservers. A good way to prevent these networks from communicating with each other is by implementing VLANs on the core switch, preventing hosts located in one VLAN from communicating with hosts in another, without some form of bridge or gateway to connect both virtual networks.
The first configuration we'll look at builds on where we left off in the previous getting started guide. The firewall has Layer 3 interfaces and we're now going to change the trust interface so it can communicate with a trunked switch interface.
The difference between a regular, or access, switchport configuration and a trunked switchport, is that the accessport will not tamper with the Ethernet header with any packets, whereas a trunkport will attach a VLAN tag in the form of a IEEE 802.1Q header to packets. This ensures that packets retain VLAN information outside the switch and should be treated as different LAN networks by the next host receiving these packets.
We'll be switching our configuration from a regular interface to tagged subinterfaces.
1. Creating subinterfaces
The first step is to remove the IP configuration from the physical firewall.
Navigate to the Network tab.
Go to Interfaces on the left pane.
Open the interface configuration.
Navigate to the IPv4 tab.
Select the subnet.
We can now go ahead and add a subinterface.
In the subinterface configuration, we need to assign an interface number and a tag. The tag needs to match the VLAN exactly, but the interface number may be different. For ease of management, it's best to set it the same id as the VLAN tag. Add the interfaceto the 'default' Virtual Router and assign it to the 'trust' Security Zone.
Next, navigate to the IPv4 tab and add the IP to the interface.
Then navigate to the Advanced tab and set the Management Profile to 'ping.'
Next, we've added a webserver to the network and placed it in VLAN 200 on the switch.
So we'll need to add a second subinterface and set it to VLAN tag 200. We'll also create a new Security Zone so we can apply different security policy to it.
We'll call the new zone 'dmz'
and assign the interface a different IP subnet
and we'll also set the Management Profile to 'ping.'
Your interface configuration should now look similar to this:
2. Reconfigure DHCP
We will now need to move the DHCP server we created last time to the new subinterface.
Navigate to the Network tab.
Open DHCP menu from the left pane.
Open the DHCP configuration for interface ethernet1/2.
Change the Interface to ethernet1/2.100 to match the new subinterface.
3. Create a new NAT policy
The next step is to create a NAT policy to allow hosts on the internet to reach the webserver via the external IP address of the firewall.
Navigate to the Policies tab.
Open NAT configuration from the left pane.
Click Add to create a new NAT policy.
In the Original Packet tab, we set the source and destination zones to untrust, and the destination address to the external IP address of the firewall. The destination zone is untrust because the firewall will try to determine the destination zone of a received packet based on its routing table. In this case, the original destination IP address, before NAT is applied, belongs to the untrust zone.
In the Translated Packet tab, we add the physical IP addres of the webserver.
4. Add security policy
The last step is to create security policies to allow the trust and untrust zone to access the webserver.
Navigate to Policies.
Open the Security policies from the left pane.
Click Add to create a new rule and name it access_to_webserver.
For now, we'll set the source zone to 'untrust.'
We'll set the destination to 'dmz' and the destination address to the external IP of the firewall.
We'll enable application web-browsing.
Enable several security profiles to make sure the webserver is protected from attacks.
Repeat this step for a security policy from the trust zone, so additional applications can be added.
In the destination, we'll set Security Zone 'dmz' and the internal IP address of the webserver.
Add additional applications for management.
Your security policy should now look similar to this:
After you commit this new configuration, interface ethernet1/2 will accept 'tagged' packets for VLAN 100 and 200 and the webserver will become available to the outside world.
Thank you for reading—please leave any comments in the comment section below.
If you've enjoyed this article, please also take a look at the follow-up article: