Skip to main content

Introducing the WFP driver

· 2 min read

This post introduces the WFP (Windows Filtering Platform) driver added in Mudfish v4.5.1. The questions below explain why it was added and where to use it, without going into implementation details.

If anything in this post is incorrect or unclear, please contact us on the Mudfish Forums.

What does the WFP driver do?​

Before this driver was introduced, Mudfish could route traffic other than the intended game traffic. These articles describe typical examples:

This caused several problems:

  • Unwanted traffic could pass through Mudfish and consume a large amount of credit.
  • When a game server moved, users sometimes had to capture game packets and send them to the Mudfish administrator so the item could be updated.

The Mudfish WFP filtering driver was created to address these problems:

  • It can route only traffic generated by a specified process. For example, watching Twitch while playing Overwatch no longer consumes credit for unrelated Twitch traffic.
  • It can handle new game destinations without a separate packet dump.
  • It makes it easier to use Mudfish with games that are not officially supported.

Which operating systems are supported?​

The driver supports the following operating systems:

  • Windows XP: does not work
  • Windows Vista SP2: does not work
  • Windows 7: does not work
  • Windows 8: works
  • Windows 8.1: works
  • Windows 10: works

Linux and Mac OS X are not supported.

Current WFP Item mode support

The information above describes the Windows WFP driver as it was in 2019. WFP Item mode is now supported on Linux in Mudfish v6.2.0 or later and on macOS in Mudfish v6.5.0 or later. On macOS, the operating system must be 11.5 or later.

For details on supported platforms and how to enable it, see WFP Item mode.

How do I use it?​

No special setup is required. It is applied automatically when you use Mudfish v4.5.1 or later.

To create your own item, see Create Custom Item.