By Manny Fernandez

May 14, 2020

VWire with FortiGate Firewalls

Although the FortGate CAN operate in transparent mode, I rarely used/use it.  Fortinet introduced VWire which is a layer 2 pair of interfaces.  These interfaces do NOT have an IP address assigned to either of them. You cannot add VLANs to virtual wire pairs. However, you can enable wildcard VLANs for a virtual wire pair. This means that all VLAN-tagged traffic can pass through the virtual wire pair if allowed by virtual wire pair firewall policies.  Essentially, it is similar to a transparent mode VDOM but better, less complex, and cleaner IMHO.

Use Case:

This is ONE Use Case but the possibilities are endless.  Lets say you have 20 locations and they are all connected via an MPLS circuit.  The remote sites are a hybrid of Trusted and Hostile sites meaning that they are known to have issues with Shadow IT…. (the ones NOT running FortiNAC, but that is a subject for a different post 😊 ).  You want to make sure that you are able to run IPS against that traffic to try to protect the “soft and chewy center” of your datacenter.  Lets say that the MPLS terminates at the DC on a carrier managed router.  You could disconnect the router from the internal network and plug it into one side of the FortiGate VWire and then plug the other side of the FortiGate VWire to the internal network.  Now you can enforce and inspect traffic as it flows from remote sites to internal and internal to remote sites.

Another Use Case, which we describe below, is blocking RDP access from the standard users.  Here we will block all RDP sessions destined to the Server VLAN and permit everything else.

Configuring the VWire

You will need to create the VWire pair by going to Network then Interface

2020-05-14_17-23-25.png

Choose Create New

2020-05-14_17-24-17 (1).png

Then choose Virtul Wire Pair

2020-05-14_17-25-20.png

Give it a Name and choose the Interface Members  Note:  The interfaces cannot have any configuration on them or be referenced anywhere else in the config.

2020-05-14_17-25-40.png

If you plan on using Wildcard VLANs select it and choose the VLANs.  Enter the VLAN (e.g. 1-1024)

2020-05-14_17-25-57.png

2020-05-14_17-28-16.png

Never mind the selected Wildcard VLAN as it was switched off after I added the interfaces.

2020-05-14_17-31-53.png

You will now have a section in the Networks | Interfaces portion of the Fortigate that will show the VWire named Monkey-VW and the two corresponding interfaces.

2020-05-14_21-34-20.png

Creating Policies

The VWire policies are located in the same general area as the IPv4 Policies (or the new Policies in 6.4+) but in their own section.

2020-05-14_17-38-38

The section is called Firewall Virtual Wire Pair Policy

2020-05-14_20-53-04.png

On the top, right hand side of the screen, you will see the name of the VWire Pair we created in the first section.

2020-05-14_17-38-38.png

Now you can Create New

2020-05-14_17-39-30.png

This section is pretty much the same as what you are used to seeing whether you are running Policy-Based or Profile-Based modes, with this major difference; you will see the Virtual Wire Pair instead of incoming interface and outgoing interface.

In this section, you will be able to create either unidirectional or bidirectional policy.  In our example, we are going to assume that port9 is connected to common user PCs and port10 is connected to the Server side.

2020-05-14_17-41-28.png

We are going to create an address object for the PC-Network represented by the 10.1.11.0/24 subnet.

2020-05-14_17-42-56.png

Above we can see the policy I am creating that will deny all the PCs in the PC-Network from using RDP to connect to the SERVER-LAN.  Since the policy is a Deny we will not see any security profiles or Applications (In policy-mode).

2020-05-14_21-23-36.png

In the screenshot above, we can see that all traffic from the PC-Network (Port9) destined to SERVER-LAN (Port10) that is RDP (TCP 3389) will be denied.  All other traffic back and forth will be permitted.

You can have multiple VWire configurations without the need for VDOMs.  I use this configuration regularly.  It is great to put the FortiGate between existing firewalls and internal switches or perimeter router.  I love to identify traffic that “competitors” do not see.

Hope this helps.

 

 

Recent posts

  • If you've spent any time configuring user authentication on... Full Story

  • DNS is one of those technologies that quietly underpins... Full Story

  • BGP issues on FortiGate firewalls usually trace back to... Full Story

  • Every time your laptop talks to your router, a... Full Story

  • If you've spent any time configuring NAT on a... Full Story

  • If you have spent any time configuring firewall policies... Full Story

  • High availability on FortiGate is one of those features... Full Story

  • If you've configured SD-WAN on a FortiGate, you've almost... Full Story

  • FortiLink is the management protocol that turns a FortiSwitch... Full Story

  • FortiSwitches are pretty rock solid from Mean Time Between... Full Story

  • This is a quicky tip.  Have you ever gone... Full Story

  • DNS is one of those quiet pieces of internet... Full Story

  • This article is an updated version of the previous... Full Story

  • You will add ns2 as a secondary (slave) BIND9... Full Story

  • In the process of deploying my lab, I needed... Full Story

  • RFC 8805, used to be known as Self-Correcting IP... Full Story

  • Years back, I wrote an article about certificate pinning. ... Full Story

  • FortiGates have the ability to send alerts to Microsoft... Full Story

  • In this post, I am going to walk through... Full Story

  • Troubleshooting VoIP on a FortiGate can feel like trying... Full Story

  • Prior to FortiOS 7.0, there were three commands to... Full Story

  • In this post, I am going to go over... Full Story

  • What we are going to do:  We are going... Full Story

  • Choosing between FGCP (FortiGate Clustering Protocol) and FGSP (FortiGate... Full Story

  • Creating a VLAN on macOS (The "Pro" Move) A... Full Story

  • This blog post explores the logic behind how macOS... Full Story

  • Pretty Fly for a Wi-Fi Tell My Wi-Fi Love... Full Story

  • Part of my daily gig is creating BoMs (Bill-of-Materials)... Full Story

  • ICMP introduces several security risks, but careful filtering, rate... Full Story

  • The command diag debug application dhcps -1 enables full... Full Story

  • In the world of FortiOS, execute tac report is... Full Story

  • LLDP; What is it The Link Layer Discovery Protocol... Full Story

  • What it actually does When you run diagnose fdsm... Full Story

  • Monkey Bites are bite-sized, high-impact security insights designed for... Full Story

  • I have run macOS in macOS with Parallels but... Full Story

  • Don't be confused with my other FortiNAC posts where... Full Story

  • This is the third session in a multi-part article... Full Story

  • Today I was configuring key-based authentication on a FortiGate... Full Story

  • Netcat, often called the "Swiss Army knife" of networking,... Full Story

  • At its core, IEEE 802.1X is a network layer... Full Story

  • In case you did not see the previous FortiNAC... Full Story

  • This is our 5th session where we are going... Full Story

  • Now that we have Wireshark installed and somewhat configured,... Full Story

  • The Philosophy of Packet Analysis Troubleshooting isn't about looking... Full Story

  • Overview FortiOS 8.0 introduces custom tags as a first-class... Full Story

  • These are two distinct mechanisms on FortiOS, and conflating... Full Story

  • Replacement messages are the pages and text blocks that... Full Story