<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Internet content filtering solutions for business - WFilter Blog</title>
	<atom:link href="http://blog.wfilterngf.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://blog.wfilterngf.com</link>
	<description>Internet content filter and firewall solutions for business network.</description>
	<lastBuildDate>Sat, 21 Nov 2026 02:00:22 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.8.5</generator>
	<item>
		<title>WFilter NG Firewall in VMware: What You Must Know About Bandwidth and Gateway Mode</title>
		<link>http://blog.wfilterngf.com/?p=693</link>
		<comments>http://blog.wfilterngf.com/?p=693#comments</comments>
		<pubDate>Sat, 21 Nov 2026 02:00:21 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=693</guid>
		<description><![CDATA[If you&#8217;re eager to try WFilter NG Firewall, spinning it up in VMware seems like a quick win. But before you rely on virtual testing, there are two pitfalls that can waste your time: the hidden bandwidth cap and the gateway/DHCP setup. Let&#8217;s dive into these real-world scenarios. 1. The Bandwidth Halving Trap in Virtual [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>If you&#8217;re eager to try WFilter NG Firewall, spinning it up in VMware seems like a quick win. But before you rely on virtual testing, there are two pitfalls that can waste your time: the hidden bandwidth cap and the gateway/DHCP setup. Let&#8217;s dive into these real-world scenarios.</p>
<h2>1. The Bandwidth Halving Trap in Virtual Machines</h2>
<p>Imagine you have a 100Mb network connection. You install WFilter NG Firewall in VMware, run a speed test, and see only 50Mb throughput. You might think the firewall is slow—but it&#8217;s not. The VM environment itself is the bottleneck.</p>
<p>In a virtual machine, both outgoing and incoming traffic share the same virtual cable. So if your physical network link is 100Mb, the maximum bandwidth you can get through the VM is 50Mb. This is a critical limitation for preview testing: you cannot judge the real performance of WFilter NG Firewall based on VM results.</p>
<p>Use VMs only to explore features, not to benchmark throughput. For accurate performance testing, install WFilter NG Firewall on a physical PC.</p>
<p><img src='http://wiki.wfilterngf.com/images/c/c9/Vmware1.png' alt='Creating WFilter NG Firewall virtual machine in VMware'><br />
<h2>2. Gateway Mode and DHCP: Avoiding Network Conflicts</h2>
<p>WFilter NG Firewall must run in &#8216;gateway&#8217; mode inside a VM. That means it sits between your clients and the internet, inspecting traffic. But here&#8217;s the catch: your existing network probably has its own gateway and DHCP server.</p>
<p>Suppose your subnet is 192.168.1.x with gateway 192.168.1.1. In the WFilter NG Firewall setup wizard, you choose &#8216;Gateway&#8217; and assign a static IP to the WAN interface (e.g., 192.168.1.2). Then you need to point client devices to the firewall&#8217;s LAN IP (192.168.10.1) as their gateway. If a client still uses the old gateway, WFilter cannot control it.</p>
<p>The bigger pain point: an existing DHCP server. If your network already has one, it will keep handing out the old gateway to clients. You must disable it so WFilter NG Firewall becomes the DHCP server. Then all clients with dynamic IPs will be redirected automatically.</p>
<p>This step is easy to overlook during a quick VM test, leading to confusion: &#8216;Why isn&#8217;t the firewall blocking anything?&#8217; The answer is usually a DHCP conflict or a misconfigured gateway.</p>
<p><img src='http://wiki.wfilterngf.com/images/4/42/Vmware4.png' alt='Final virtual machine settings for WFilter NG Firewall'>
<p>By keeping these two points in mind—bandwidth limits and gateway/DHCP setup—you can avoid false conclusions and get the most out of your VMware preview of WFilter NG Firewall.</p>
<p>Source: <a href="http://wiki.wfilterngf.com/VMWareInstallation">http://wiki.wfilterngf.com/VMWareInstallation</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=693</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Multi-WAN Load Balancing: How Policy Rules and WAN Failover Actually Work</title>
		<link>http://blog.wfilterngf.com/?p=691</link>
		<comments>http://blog.wfilterngf.com/?p=691#comments</comments>
		<pubDate>Wed, 18 Nov 2026 02:00:16 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=691</guid>
		<description><![CDATA[Three internet lines, one router, and still everyone complains. That is the moment most network admins finally open the Multi-WAN module. The idea is simple: define a few line solutions, then tell the router which traffic should use which one. But the part that trips people up is not the balancing itself — it is [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Three internet lines, one router, and still everyone complains. That is the moment most network admins finally open the Multi-WAN module. The idea is simple: define a few line solutions, then tell the router which traffic should use which one. But the part that trips people up is not the balancing itself — it is the policy layer and the failover setting. Let&#8217;s look at both.</p>
<p><img src="http://wiki.wfilterngf.com/images/5/5e/Ros_mwan_002.png" alt="Multi-WAN solution and policy configuration screen" /></p>
<h2>1. Line Solutions Only Work When Policies Point Traffic At Them</h2>
<p>You start by creating line solutions. Maybe you want one dedicated WAN for business servers, a second solution that balances two lines for office users, and a third that sends specific websites out through a single link. Each solution holds its own load balancing rank per interface. So far, so good.</p>
<p>Here is the catch: a solution does nothing on its own. Traffic only lands in it because a policy matched. A policy answers three questions — where the traffic comes from, where it is going, and which ports it uses.</p>
<ul>
<li><strong>Source</strong> — choose <em>Any</em>, <em>Single IP</em>, or <em>IP Range</em>. Single IP accepts both a host address like 192.168.1.10 and a subnet like 192.168.1.0/24, which is handy when you want a whole floor or department on one line.</li>
<li><strong>Target</strong> — same syntax options for an IP or domain, plus a <em>Customize</em> mode that lets you pick by application type, web categories, countries and regions, or custom IPs and domains.</li>
<li><strong>Ports</strong> — the destination ports the rule applies to.</li>
</ul>
<p>The single most important behaviour to internalise is ordering. Rules are processed from the top of the list downward, and the first match wins. That means a broad &#8220;any source, any target&#8221; rule sitting at the top will quietly swallow every rule beneath it. When a policy appears to be ignored, nine times out of ten it is simply being outranked. Drag the re-order icon to move rules up or down, and re-test after every change.</p>
<p>A practical habit: put the narrow, high-priority rules first — the business server that must stay on its own line, the site that must always exit through a specific WAN — and let the general &#8220;everyone else, balanced&#8221; rule sit at the very bottom as the catch-all.</p>
<h2>2. WAN Failover Is Off By Default — Turn It On</h2>
<p>Load balancing distributes traffic, but it does not protect you when a line dies. That is a separate feature, and it is disabled unless you enable it.</p>
<p>When WAN Failover is active, the router continuously checks line availability. If an interface stops responding, the load weighting is re-balanced across the remaining lines so users keep working instead of staring at a spinner.</p>
<ul>
<li>Enable <strong>reconnect</strong> and the WAN interface will be automatically restarted after a failure — useful for flaky PPPoE lines that recover on their own.</li>
<li>For a <strong>static IP</strong> WAN interface, the system automatically pings the WAN gateway to verify the link.</li>
<li>Prefer IP addresses over domain names for connection testing. A DNS-based check can fail for reasons unrelated to the line itself, which triggers unnecessary failovers.</li>
</ul>
<p><img src="http://wiki.wfilterngf.com/images/5/5b/Ros_mwan_003.png" alt="WAN failover detection settings" /></p>
<p>The same advice applies to the detection targets: a public, stable IP that you control or trust is a far better health signal than a hostname that depends on a resolver working.</p>
<p>Get these two pieces right — ordered policies that send the right traffic down the right solution, and failover that catches the line that drops at 2 a.m. — and the multi-WAN setup stops being a source of tickets and starts being something you forget about.</p>
<p>Source: <a href="http://wiki.wfilterngf.com/Mwan">http://wiki.wfilterngf.com/Mwan</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=691</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WFilter NG Firewall Domain Controller Connection Failed? Fix AD Integration</title>
		<link>http://blog.wfilterngf.com/?p=689</link>
		<comments>http://blog.wfilterngf.com/?p=689#comments</comments>
		<pubDate>Mon, 16 Nov 2026 02:00:20 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=689</guid>
		<description><![CDATA[It usually happens at the worst time. You open WFilter NG Firewall, expecting Active Directory integration to be running as usual, and instead you see a blunt message: Failed to connect domain controller. User identification stops working, and now you are troubleshooting instead of managing the network. The source of the problem is straightforward: WFilter [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>It usually happens at the worst time. You open WFilter NG Firewall, expecting Active Directory integration to be running as usual, and instead you see a blunt message: <strong>Failed to connect domain controller</strong>. User identification stops working, and now you are troubleshooting instead of managing the network.</p>
<p>The source of the problem is straightforward: WFilter NG Firewall cannot retrieve information from the domain controller. That does not mean the firewall is broken. It means the AD Integration settings need a close look.</p>
<h2>1. What the error actually means</h2>
<p>In plain terms, WFilter needs to talk to your domain controller so it can pull the information it needs. When that conversation fails, AD Integration cannot do its job. The fix is not a deep firewall rule change. It is almost always a settings check inside AD Integration.</p>
<h2>2. Start with the domain controller IP address and port</h2>
<p>This is the first thing I check, because it is easy to break without noticing. If your domain controller was migrated, rebuilt, or replaced, the IP address in WFilter may still point to the old server. The credentials can look perfect and the error will still appear.</p>
<p>Open the AD Integration settings and confirm that the domain controller IP address and port are correct. Make sure they match the domain controller WFilter should be querying. A wrong IP address sends every request to the wrong place. A wrong port means the request reaches the right server but not the service WFilter needs. I have seen both cases produce the same connection failure message, which is why this check comes first.</p>
<p>Do not assume that because the network is up, the integration is fine. The firewall may be able to reach the server generally, yet still fail on the specific address and port configured for AD Integration. Correct those fields, save the settings, and test again.</p>
<h2>3. The admin account must belong to Domain Admins</h2>
<p>This is the detail that catches many people. You can enter a username and password that are completely valid, and WFilter can still fail to connect. Why? Because the configured admin account must belong to the <strong>Domain Admins</strong> group.</p>
<p>In one case, a team used a delegated service account that worked for other tools. The username was right, the password was right, but WFilter still could not retrieve domain controller information. Once the account was added to the Domain Admins group, the integration started working. That one group membership change solved the problem.</p>
<p>So check two things together: the admin username and password are correct, and the account is a member of Domain Admins. If the password was recently changed, update it in WFilter as well. A valid account outside the required group is still not enough for this integration.</p>
<h2>4. Re-test after the fix</h2>
<p>After correcting the domain controller IP address and port, and confirming the admin account belongs to Domain Admins, save the AD Integration settings and run the connection test again.</p>
<ul>
<li>Confirm the domain controller IP address and port.</li>
<li>Confirm the admin username and password.</li>
<li>Confirm the account is in the Domain Admins group.</li>
</ul>
<p>If the error returns, revisit these same two areas before changing anything else. In most cases, the failed connection is not a mystery. It is a settings mismatch between WFilter NG Firewall and the domain controller.</p>
<p>Source: <a href="http://wiki.wfilterngf.com/DCQUERY_FAILURE">http://wiki.wfilterngf.com/DCQUERY_FAILURE</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=689</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IKEv2 VPN Setup Guide: WAN IP, VPN Subnet, and Firewall Rules</title>
		<link>http://blog.wfilterngf.com/?p=687</link>
		<comments>http://blog.wfilterngf.com/?p=687#comments</comments>
		<pubDate>Sun, 15 Nov 2026 14:28:42 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=687</guid>
		<description><![CDATA[You roll out an IKEv2 VPN for a remote team. A colleague connects, sees the VPN icon, then opens the internal file share and gets nothing. The tunnel is up, but work is not. That is the moment to stop treating IKEv2 as a single toggle and check the server plan behind it. The IKEv2 [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>You roll out an IKEv2 VPN for a remote team. A colleague connects, sees the VPN icon, then opens the internal file share and gets nothing. The tunnel is up, but work is not. That is the moment to stop treating IKEv2 as a single toggle and check the server plan behind it.</p>
<p>The IKEv2 Server feature provides a dial-in VPN service based on IKEv2+MSCHAPv2 authentication. It needs public internet IP address(es), so the first practical question is not which client app to use, but which public address the service will listen on.</p>
<h2>1. Plan the WAN IP, VPN Subnet, and Push Route Before You Connect</h2>
<p>In the server settings, WAN IP is where you choose the WAN IP address that runs the IKEv2 service. VPN Subnet is the address pool for VPN clients, such as 10.7.1.0/24. Push Route defines routing for clients. Those three fields answer different questions: where the service is reachable, where clients sit, and which networks clients should reach through the tunnel.</p>
<p><img src='http://wiki.wfilterngf.com/images/8/86/Ikev2_server.png' alt='IKEv2 server settings showing WAN IP, VPN subnet, and push route'>
<p>The pain point shows up when only the first two fields get attention. A client can connect successfully and still fail to reach an internal resource because the route was never pushed. If you are setting this up for a branch office or a support team, treat the VPN subnet and push route as part of the same design conversation. Write them down, apply them in the server settings, and test from a real client instead of assuming that a connected status means full access.</p>
<h2>2. Why IKEv2 Clients Need Firewall Rules, Not Just a Login</h2>
<p>The second trap is firewall policy. To allow IKEv2 clients to access the network, you also need to set up firewall policies in Firewall -> Rules. This is easy to miss because VPN authentication and firewall permission are separate steps. The user account can be valid, the tunnel can be established, and traffic can still be blocked at the firewall.</p>
<p><img src='http://wiki.wfilterngf.com/images/4/49/Ikev2_firewall.png' alt='Firewall rules page for allowing IKEv2 VPN client access'>
<p>From the user perspective, that feels like a broken VPN. From the admin perspective, it is usually a missing rule. Before you tell someone the VPN is ready, confirm that the firewall policies allow the access you intend. Then test the exact resource the user needs, not just the connection screen. A small amount of planning around the WAN IP, VPN subnet, push route, and firewall rules saves a lot of back-and-forth later.</p>
<p>Source: <a href="http://wiki.wfilterngf.com/IKEv2">http://wiki.wfilterngf.com/IKEv2</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=687</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WFilter Exceeds License Limit: What It Means and How to Fix It</title>
		<link>http://blog.wfilterngf.com/?p=685</link>
		<comments>http://blog.wfilterngf.com/?p=685#comments</comments>
		<pubDate>Sun, 15 Nov 2026 14:25:32 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=685</guid>
		<description><![CDATA[It usually starts with a quick glance at WFilter: a small alert reads “Exceeds license limit.” If you manage an enterprise network, this is more than a cosmetic warning. It means the number of online client devices has crossed the limit allowed by your enterprise license. The tricky part is that the internet does not [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>It usually starts with a quick glance at WFilter: a small alert reads “Exceeds license limit.” If you manage an enterprise network, this is more than a cosmetic warning. It means the number of online client devices has crossed the limit allowed by your enterprise license.</p>
<p>The tricky part is that the internet does not stop. Users can still browse, stream, and download. That can make the alert easy to postpone—until you realize what it means for your filtering policies.</p>
<h2>1. Why the “Exceeds License Limit” Warning Appears</h2>
<p>This message only exists in the enterprise license. WFilter is counting online client devices, and when that count goes above your licensed number, the warning appears. In a busy office, that can happen faster than expected: new hires receive laptops, contractors connect during a project, guest devices join the Wi-Fi, or temporary equipment comes online for a few days.</p>
<p>Because the message is specific to enterprise licensing, it is a clear signal that your device count no longer matches your license coverage. The fix is straightforward: get a license that covers more users. But before you buy, it helps to understand what happens to the devices that are already over the limit.</p>
<h2>2. What Happens to Over-Limit Clients—and Why It Matters</h2>
<p>For clients that exceed the license limit, internet access is still available, except there is no blocking nor monitoring. In other words, the extra devices stay online, but your filtering controls do not apply to them.</p>
<p>That is the real pain point. Your network feels fine because connectivity remains, so users may not report a problem. Meanwhile, those over-limit devices can bypass the blocking and monitoring you expect to be in place. A contractor laptop, a temporary workstation, or a newly added device may be online without the visibility and controls you rely on.</p>
<p>The solution is to get a more user license. If the overage is permanent—new staff, more devices, expanded operations—upgrade the license to match your actual online client count. If the overage is temporary, remember that excess clients are still unfiltered while they remain online. Either way, the alert is a reminder to bring your license coverage back in line with your network.</p>
<ul>
<li>Check whether the overage is temporary or permanent.</li>
<li>Confirm the number of online client devices.</li>
<li>Get a more user license to restore full blocking and monitoring coverage.</li>
</ul>
<p>Source: <a href="http://wiki.wfilterngf.com/OUTOFLICENSE">http://wiki.wfilterngf.com/OUTOFLICENSE</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=685</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WFilter NG Firewall Installation Guide: Gateway vs. Bridge Deployment</title>
		<link>http://blog.wfilterngf.com/?p=683</link>
		<comments>http://blog.wfilterngf.com/?p=683#comments</comments>
		<pubDate>Sun, 15 Nov 2026 14:15:04 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=683</guid>
		<description><![CDATA[Setting up a network firewall can feel overwhelming, especially when you&#8217;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&#8217;t [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Setting up a network firewall can feel overwhelming, especially when you&#8217;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&#8217;t the installation itself; it was deciding <em>where</em> to put it. If you&#8217;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.</p>
<h2>1. Choose Your Deployment: Gateway or Bridge?</h2>
<p>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.</p>
<ul>
<li><strong>As a network gateway:</strong> WFilter replaces your current gateway. This means it becomes the primary device that routes traffic between your internal network and the internet. You&#8217;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.</li>
<li><strong>As a network bridge:</strong> WFilter sits between your current gateway and your switch, bridging the two. In this mode, you don&#8217;t replace your existing gateway—you just insert WFilter inline. It&#8217;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.</li>
</ul>
<p>Which one should you choose? If you&#8217;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&#8217;d need a different product—WFilter&#8217;s internet content filter—so keep that in mind.</p>
<h2>2. Install WFilter NG Firewall on a Physical PC or Virtual Machine</h2>
<p>Once you&#8217;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.</p>
<ul>
<li><strong>Physical PC:</strong> 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.</li>
<li><strong>Virtual Machine:</strong> 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.</li>
</ul>
<p>After installation, you&#8217;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.</p>
<h2>3. Get Started After Installation</h2>
<p>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&#8217;t work, check your cabling and interface assignments first—that&#8217;s where most issues pop up.</p>
<p>Installing WFilter NG Firewall isn&#8217;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&#8217;ll have your firewall up and filtering in no time.</p>
<p>Source: <a href="http://wiki.wfilterngf.com/NewUser">http://wiki.wfilterngf.com/NewUser</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=683</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Internet Filtering Exceptions: Whitelist IPs, Domains, and Apps Without Weakening Network Security</title>
		<link>http://blog.wfilterngf.com/?p=681</link>
		<comments>http://blog.wfilterngf.com/?p=681#comments</comments>
		<pubDate>Sun, 15 Nov 2026 14:11:41 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=681</guid>
		<description><![CDATA[You deploy an internet monitoring and firewall policy to protect the business. The next morning, the support team cannot reach a payment gateway, the marketing team cannot upload campaign assets, and a developer is blocked from an API endpoint. A blanket block looked simple on paper, but it is now costing real work. This is [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>You deploy an internet monitoring and firewall policy to protect the business. The next morning, the support team cannot reach a payment gateway, the marketing team cannot upload campaign assets, and a developer is blocked from an API endpoint. A blanket block looked simple on paper, but it is now costing real work. This is where internet filtering exceptions become a practical safety valve: they let you keep network security tight while allowing the specific traffic that keeps the business moving.</p>
<h2>1. Why Internet Filtering Exceptions Matter for Network Security</h2>
<p>Most teams do not need to disable filtering every time someone hits a blocked site. They need a controlled way to say, “This IP, domain, port, or application is allowed, and other policies should not override it.” In WFilter NGF, the exception settings do exactly that: whitelisted content is not blocked by other policies. You can choose to except either IP/Domains or applications, which keeps the rule set focused instead of turning into an unmanaged allow-all.</p>
<p><img src="http://wiki.wfilterngf.com/images/8/8d/Exception001.png" alt="Exception settings for internet filtering whitelist">
<p>The pain point is familiar: the firewall is doing its job, but the exception list is the difference between a security policy people trust and one they constantly ask you to bypass. When exceptions are precise, internet monitoring stays useful and the firewall remains credible.</p>
<h2>2. How to Whitelist IPs, Domains, and Applications Correctly</h2>
<p>The syntax is where many administrators get into trouble. The goal is not to whitelist the whole internet; it is to whitelist the smallest useful target. WFilter’s exception list accepts a few simple patterns, each suited to a different scenario:</p>
<ul>
<li>One domain per line. Wildcards <code>*</code> and <code>?</code> are supported, which helps with partner portals and regional subdomains.</li>
<li>One IP address per line. No wildcard is allowed, and all traffic to that IP is whitelisted.</li>
<li><code>IP:port</code> allows only a certain port on a certain IP, useful for a specific service rather than the whole host.</li>
<li><code>*:port</code> whitelists all traffic on that port, which can fit a known application port but needs care.</li>
<li>A subnet entry, such as <code>120.55.165.0/24</code> or <code>120.55.165.*</code>, whitelists all traffic to that subnet.</li>
<li><code>*:*</code> whitelists all traffic. That is an emergency lever, not a daily setting.</li>
</ul>
<p>In real deployments, the most common mistake is reaching for <code>*:*</code> because a single domain is blocked. A better move is to add the exact domain or the specific IP:port. This keeps internet filtering effective and avoids a firewall policy that looks strict but has a wide-open exception.</p>
<h2>3. Use “**domain” and “-domain” to Keep Exceptions Precise</h2>
<p>Two syntax options are especially useful when a domain depends on multiple IP addresses or when you need to carve out a single subdomain. The first is <code>**domain</code>, for example <code>**www.wfilterngf.com</code>. This whitelists the domain and also whitelists the IP addresses that the domain resolves to. That matters because modern sites often load resources from changing IPs, and an IP-only exception can break silently when the address changes. Using <code>**domain</code> gives you a more durable exception without opening an entire subnet.</p>
<p>The second is <code>-domain</code>, which is an exception to exceptions. Wildcards are supported, so you can exclude a specific host from a broader whitelist. For example, if you have whitelisted a parent domain but want to keep <code>news.wfilterngf.com</code> blocked, you can add <code>-news.wfilterngf.com</code>. This is a small feature with a big operational payoff: you can satisfy a business request without losing control of the category or host you intentionally wanted to restrict. In network security terms, it is the difference between a blunt allow rule and a surgical one.</p>
<p>Exceptions are not a weakness in your internet filtering strategy—they are how you keep it usable. Start with the narrowest domain, IP, port, or application, document why it exists, and use <code>**domain</code> and <code>-domain</code> when you need precision. Your firewall stays firm, your internet monitoring stays meaningful, and your users stop filing the same unblock ticket every week.</p>
<p>Source: <a href="http://wiki.wfilterngf.com/Exception">http://wiki.wfilterngf.com/Exception</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=681</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Internet Usage Monitoring: Policies, Recording Options, and Advanced Settings</title>
		<link>http://blog.wfilterngf.com/?p=677</link>
		<comments>http://blog.wfilterngf.com/?p=677#comments</comments>
		<pubDate>Sun, 15 Nov 2026 14:06:32 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=677</guid>
		<description><![CDATA[The Internet Usage Monitoring module records internet activity, including Web Surf, Web Post, Outgoing Emails, Incoming Emails, File Upload History, File Download History, FTP/Telnet Sessions, IP-MAC History, and Connection Details. It works in both gateway mode and bridge mode. An Enterprise license is required. Recording Policy Multiple policies can apply to the same client. For [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The Internet Usage Monitoring module records internet activity, including Web Surf, Web Post, Outgoing Emails, Incoming Emails, File Upload History, File Download History, FTP/Telnet Sessions, IP-MAC History, and Connection Details.</p>
<p>It works in both gateway mode and bridge mode. An Enterprise license is required.</p>
<p><img src='http://wiki.wfilterngf.com/images/6/68/Wfrecorder_query1.png'><br />
<h2>Recording Policy</h2>
<p>Multiple policies can apply to the same client. For example, policy A could record web surfing for an entire subnet, while policy B enables email recording for one special IP in that subnet. For that IP, both web surfing recording and email recording are enabled.</p>
<p><img src='http://wiki.wfilterngf.com/images/c/cb/Wfrecorder_query2.png'><br />
<h2>Web Recording</h2>
<ul>
<li><strong>Web Surf:</strong> records titles of visited web pages for HTTP websites. For HTTPS websites, only domains are recorded by default. To record HTTPS webpages, check SSL Inspector.</li>
<li><strong>Web Post:</strong> records web post content for HTTP websites. To record posts on HTTPS websites, check SSL Inspector.</li>
<li><strong>Web Post Size Limit:</strong> web posts that exceed the size limit are not recorded.</li>
<li><strong>Smart Filter:</strong> when enabled, WFilter does not record visits by non-human clients; this is not 100% accurate.</li>
<li><strong>Domains Exception:</strong> domains in the exception list are not recorded. Wildcards *? are supported.</li>
</ul>
<p><img src='http://wiki.wfilterngf.com/images/5/5f/Wfrecorder_query3.png'><br />
<h2>Email Recording</h2>
<ul>
<li>Supported email types: SMTP, POP3, IMAP4, and outgoing web-based emails.</li>
<li>For emails that exceed the size limit, only subject, from, and to are recorded.</li>
<li>To record SSL emails such as SMTP, POP, or IMAP over SSL, check SSL Inspector.</li>
</ul>
<h2>File Transfers</h2>
<ul>
<li>Supported file transfers: FTP upload, FTP download, Web download, and Web upload.</li>
<li>WFilter records only filenames or URLs for downloaded files. Full file content can be recorded for uploaded files.</li>
<li>For uploaded files that exceed the size limit, only filenames are recorded.</li>
<li>To record files transferred via HTTPS, enable HTTPS Inspector.</li>
</ul>
<p><img src='http://wiki.wfilterngf.com/images/e/ed/Wfrecorder_queryftp.png'><br />
<h2>Other Activity Options</h2>
<ul>
<li>Options are available to enable IM accounts and FTP/Telnet sessions.</li>
<li>Only QQ messenger IDs can be recorded.</li>
<li>When FTP/Telnet Sessions is enabled, sent FTP/Telnet commands can be recorded.</li>
<li>IP-MAC History keeps a daily IP-MAC address history.</li>
<li>Connections provides detail of TCP connection history.</li>
</ul>
<p><img src='http://wiki.wfilterngf.com/images/e/ec/Wfrecorder_querysessions.png'><img src='http://wiki.wfilterngf.com/images/3/39/Wfrecorder_queryconnections.png'><br />
<h2>Advanced Settings</h2>
<ul>
<li><strong>IPv6:</strong> enable recording of IPv6 activity.</li>
<li><strong>Database Commit:</strong> sets the database commit frequency.</li>
<li><strong>Record local visits to below Hosts:</strong> local traffic to these hosts is recorded.</li>
<li><strong>Additional Webmail Domains:</strong> custom webmails to be recorded.</li>
<li><strong>Protocol Ports:</strong> customize protocol ports for HTTP, HTTPS, POP3, IMAP4, and SMTP.</li>
</ul>
<p>Source: <a href="http://wiki.wfilterngf.com/Wfquery">http://wiki.wfilterngf.com/Wfquery</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=677</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to diagnose the causes of traffic blocking in WFilter?</title>
		<link>http://blog.wfilterngf.com/?p=669</link>
		<comments>http://blog.wfilterngf.com/?p=669#comments</comments>
		<pubDate>Thu, 28 Aug 2025 05:37:57 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[How to filter internet access]]></category>
		<category><![CDATA[Network management]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=669</guid>
		<description><![CDATA[To diagnose the causes of traffic blocking in WFilter, please try below steps: 1. Check the blocking events Click bandwidth number of the client device in &#8220;Realtime bandwidth&#8221;, you will be able to see the live connections and blocking events. When an internet activity is blocked, a new blocking event will be added. So, if [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>To diagnose the causes of traffic blocking in WFilter, please try below steps:</p>
<p>1. Check the blocking events</p>
<p>Click bandwidth number of the client device in &#8220;Realtime bandwidth&#8221;, you will be able to see the live connections and blocking events.</p>
<p><a href="http://blog.wfilterngf.com/wp-content/uploads/2025/08/1.png"><img class="alignnone  wp-image-670" alt="1" src="http://blog.wfilterngf.com/wp-content/uploads/2025/08/1.png" width="1874" height="766" /></a></p>
<p><a href="http://blog.wfilterngf.com/wp-content/uploads/2025/08/2.png"><img class="alignnone size-full wp-image-671" alt="2" src="http://blog.wfilterngf.com/wp-content/uploads/2025/08/2.png" width="1593" height="751" /></a></p>
<p><a href="http://blog.wfilterngf.com/wp-content/uploads/2025/08/3.png"><img class="alignnone size-full wp-image-672" alt="3" src="http://blog.wfilterngf.com/wp-content/uploads/2025/08/3.png" width="1523" height="657" /></a></p>
<p>When an internet activity is blocked, a new blocking event will be added. So, if there is no blocking event, it means no internet access policy is applied.</p>
<p>&#8220;Rule&#8221; indicates the violated internet access policy rule. &#8220;Remarks&#8221; has the blocking reason.</p>
<p>2.  Check the policy testing</p>
<p>In &#8220;Utils&#8221;-&gt;&#8221;Policy Testing&#8221;, you can test internet access of a certain IP. So you can disgnose the blocking reason.</p>
<p><a href="http://blog.wfilterngf.com/wp-content/uploads/2025/08/4.png"><img class="alignnone size-full wp-image-673" alt="4" src="http://blog.wfilterngf.com/wp-content/uploads/2025/08/4.png" width="1318" height="834" /></a></p>
<p>3. Check &#8220;Security&#8221; history</p>
<p>&#8220;IPS(intrusion prevention system)&#8221;, &#8220;AI Defense&#8221; also can block internet access in some circumstances. So please also check history of &#8220;IPS&#8221;, &#8220;IOCs&#8221; and &#8220;AI Defense&#8221; to see whether the client is blocked.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=669</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to setup site-to-site VPN with WFilter&#8217;s SD-WAN service?</title>
		<link>http://blog.wfilterngf.com/?p=660</link>
		<comments>http://blog.wfilterngf.com/?p=660#comments</comments>
		<pubDate>Mon, 07 Jul 2025 07:08:55 +0000</pubDate>
		<dc:creator><![CDATA[WFilter]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.wfilterngf.com/?p=660</guid>
		<description><![CDATA[WFilter&#8217;s SD-WAN service is an integration of the ZeroTier networking. With SD-WAN, you are able to build secure site-to-site VPN tunnels without needing a static public IP address.  This guide will show you the necessary steps using WFilter NGF. 1. Network topology As shown in the above topology diagram, headquarter and two branches all use WFilter [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>WFilter&#8217;s SD-WAN service is an integration of the ZeroTier networking. With SD-WAN, you are able to build secure site-to-site VPN tunnels without needing a static public IP address.  This guide will show you the necessary steps using WFilter NGF.</p>
<h2>1. Network topology</h2>
<p><a href="http://blog.wfilterngf.com/wp-content/uploads/2025/07/2022021616449891141396851.png"><img class="alignnone size-full wp-image-662" alt="202202161644989114139685" src="http://blog.wfilterngf.com/wp-content/uploads/2025/07/2022021616449891141396851.png" width="587" /></a></p>
<p>As shown in the above topology diagram, headquarter and two branches all use WFilter NGF as gateway. By adding each gateway into the SD-WAN network, you will be able to setup secure site-to-site VPN tunnels.</p>
<h2>2. SD-WAN subnet settings</h2>
<p>First setup a SD-WAN network in the WFilter cloud service.</p>
<p><img alt="Sdwan network01.png" src="http://wiki.wfilterngf.com/images/thumb/e/e0/Sdwan_network01.png/450px-Sdwan_network01.png" width="450" /></p>
<p><img alt="Sdwan network02.png" src="http://wiki.wfilterngf.com/images/thumb/a/ab/Sdwan_network02.png/450px-Sdwan_network02.png" width="450" /></p>
<h2>3. Join every WFilter into the SD-WAN network</h2>
<p><a href="http://blog.wfilterngf.com/wp-content/uploads/2025/07/QQ20250707-145422.png"><img class="alignnone  wp-image-663" alt="QQ20250707-145422" src="http://blog.wfilterngf.com/wp-content/uploads/2025/07/QQ20250707-145422.png" width="800" /></a></p>
<h2>4. Assign SD-WAN ip and setup routing</h2>
<p><a href="http://blog.wfilterngf.com/wp-content/uploads/2025/07/QQ20250707-145655.png"><img class="alignnone size-full wp-image-664" alt="QQ20250707-145655" src="http://blog.wfilterngf.com/wp-content/uploads/2025/07/QQ20250707-145655.png" width="450" /></a></p>
<p>Assign static SD-WAN ip addresses to every WFilter, for example: WFilter A(10.200.188.1), WFilter B(10.200.188.2), WFilter C(10.200.188.3). Then you can setup SD-WAN routing policy to forward LAN traffic.</p>
<p><a href="http://blog.wfilterngf.com/wp-content/uploads/2025/07/QQ20250707-150606.png"><img class="alignnone size-full wp-image-665" alt="QQ20250707-150606" src="http://blog.wfilterngf.com/wp-content/uploads/2025/07/QQ20250707-150606.png" width="450" /></a></p>
<p>After the above setups, each local area network can directly access each other. To restrict access, you also can setup firewall rules in WFilter&#8217;s firewall-&gt;Rules.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wfilterngf.com/?feed=rss2&#038;p=660</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
