WFilter NG Firewall Installation Guide: Gateway vs. Bridge Deployment

Setting up a network firewall can feel overwhelming, especially when you’re not sure how it fits into your existing network. I remember the first time I tried to install WFilter NG Firewall—I had a spare PC and a vague idea that it should sit somewhere between the internet and my LAN. The tricky part wasn’t the installation itself; it was deciding where to put it. If you’re in the same boat, this guide will walk you through the two main deployment choices and the basic installation steps so you can get up and running without guesswork.

1. Choose Your Deployment: Gateway or Bridge?

Before you touch any hardware or virtual machine, you need to pick a deployment mode. WFilter NG Firewall can act as either a network gateway or a network bridge. The difference matters because it changes how traffic flows through your network.

  • As a network gateway: WFilter replaces your current gateway. This means it becomes the primary device that routes traffic between your internal network and the internet. You’ll need to reconfigure your network so that clients point to WFilter as their gateway. This mode gives you full control over filtering and monitoring, but it requires a bit more setup and a brief network interruption.
  • As a network bridge: WFilter sits between your current gateway and your switch, bridging the two. In this mode, you don’t replace your existing gateway—you just insert WFilter inline. It’s a simpler drop-in solution if you want to avoid reconfiguring every device. Traffic passes through WFilter transparently, and you still get filtering capabilities.

Which one should you choose? If you’re building a new network or want WFilter to handle routing, go with gateway mode. If you have an existing gateway you trust and just want to add filtering without disruption, bridge mode is the way to go. For pass-by deployment on a mirroring port, you’d need a different product—WFilter’s internet content filter—so keep that in mind.

2. Install WFilter NG Firewall on a Physical PC or Virtual Machine

Once you’ve picked your deployment mode, the actual installation is straightforward. WFilter NG Firewall runs on x86 hardware or in a virtual machine, so you can use a spare PC or spin up a VM in your hypervisor.

  • Physical PC: Make sure the machine meets the basic x86 requirements. Boot from the WFilter installation media and follow the on-screen prompts. The installer will guide you through disk partitioning and network interface configuration.
  • Virtual Machine: Create a new VM with sufficient CPU, RAM, and disk space, then mount the WFilter ISO as a virtual CD/DVD. Boot the VM and proceed with the same installation steps. Just remember to assign the correct virtual network adapters for your gateway or bridge setup.

After installation, you’ll need to configure the network interfaces according to your chosen mode. For gateway mode, set the WAN and LAN interfaces. For bridge mode, set up the bridge pair. The installer usually detects interfaces automatically, but double-check before finishing.

3. Get Started After Installation

With WFilter installed and networked, log in to the web interface using the credentials provided during setup. From there, you can run through the getting started wizard, which helps you configure basic policies and verify that traffic is flowing correctly. If something doesn’t work, check your cabling and interface assignments first—that’s where most issues pop up.

Installing WFilter NG Firewall isn’t hard; the key is choosing the right deployment mode for your network. Take a few minutes to plan whether you need a gateway replacement or a bridge, then follow the simple installation steps. You’ll have your firewall up and filtering in no time.

Source: http://wiki.wfilterngf.com/NewUser