WFilter ICF Installation Guide

From WFilter Documents and Tutorials
Revision as of 13:20, 31 July 2019 by WFilter (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

1 Install npcap or winpcap

WFilter ICF uses npcap/winpcap driver to capture network packets, so you need to install npcap/winpcap before installing WFilter ICF:

* For Windows 2003 and xp, please install winpcap. https://www.winpcap.org/install/default.htm
* For Windows vista and later, please install npcap. https://nmap.org/npcap/

Npcap installation steps(install npcap in WinPcap API-compatible mode):

Npcap01.png

Npcap02.png

2 Installation Note

2.1 Calculate hard disk space required

Because monitored data will be kept in your disk, so you need to calculate the required disk space and choose a proper disk to install WFilter.

Required harddisk space is related to monitored clients number and log keeping days, each monitored clients will cost about 2MByte disk space per day.

2.2 Installation of WFilter database version

If you want to install WFilter database version, you should install database first. WFilter database version supports SQL Server and MySQL database. Please refer to WFilter Database Version Guide.

3 Launching WFilter Console

You can launch WFilter console by clicking the WFilter shortcut on desktop, or run "Start" -> "Programs" -> "IMFirewall" -> "WFilter Console". Or you can type "http://127.0.0.1:10090" in your browser address bar to access WFilter console.

The default administrator user is "admin", admin password is configured during WFilter installation.

Login.png

For first time using WFilter, you will see the "Configuration Wizard", please modify certain settings following the wizard. Then you can click "online users" to check the monitored devices, as in below Figure:

Figure 3.2.jpg

The WFilter computer must be deployed at a single location in the network where it can monitor all internet traffic. Otherwise it can not work properly.

If no computer appears in "online computers", this is usually because incorrect monitoring adapter settings, please check Monitoring Settings.

If WFilter can only monitor itself, this is a deployment issue, please check "How to deploy WFilter?" for more details.


4 Deploy WFilter

4.1 Monitoring Settings

If no device presents in the "online users", there are two possibilities:

  • You haven't have any network activity yet. Please visit some websites and refresh the "Online Users" to check.
  • The monitoring adapter is configured incorrectly. As in "Figure 4.1", please run "system settings"->"check settings" to check current settings and follow the guide to fix the errors.
    Figure 4.1.jpg

4.2 How to set internet policy for monitored clients?

As in picture, click the "User-computer list". Check the "Enable Monitor" checkbox of the computer you want to monitor. You also can set blocking policy for computers in this page.

Figure 4.2.jpg


5 How to deploy WFilter?

5.1 Introduction

  • You only need to install WFilter in ONE computer to monitor the whole network. However, the WFilter computer must be deployed at a single location in the network where it can monitor all internet traffic.
  • There are two different kinds of deployment solutions:
  1. Pass-by mode: set up a mirroring port in your switch/router, and connect WFilter computer to the mirroring port to do monitoring/filtering.
  2. Pass-through mode: deploy WFilter in a windows gateway, bridge, or proxy server.
  • For more details, please check: WFilter Deployment Examples.
  • The detailed deployment depends on different network topology. Here we take a typical small network environment as an example.

5.2 A Typical Small Network

  • As in Figure 5.1, local computers use a wired router to connect to the Internet. In this type of network, it requires a port mirroring switch to be installed between the router and the switch. And the machine with WFilter installed on shall be connected to the monitor port of the port mirroring switch.
    Figure 5.1.jpg
  • For better understanding of WFilter deployment, please check: WFilter Deployment Examples.
Personal tools
Namespaces

Variants
Actions
Navigation
Tools