NetFlow · IPFIX · sFlow — filtering proxy

Your collectors should only see the flows that matter.

iFlowScreen sits between your flow exporters and collectors, dropping unwanted flows in transit — so your collectors process less, and cost less to license and run.

iflowscreen — flows in transit
SRC ADDRDST ADDRIF IN/OUTMPLSVERDICT
verdict PASS → forwarded to collectors  ·  verdict DROP → never billed, processed or stored
Overview

A transparent proxy between exporters and collectors

iFlowScreen requires no changes on the collector side. Point your exporters at it, and it forwards a filtered stream onward.

Diagram: flow exporters send NetFlow, IPFIX and sFlow packets to iFlowScreen, which filters unwanted flows and forwards the rest to flow collectors
exporters → iFlowScreen (deconstruct · filter · reconstruct) → collectors
receive

Accept UDP flow packets

From your routers, switches and other exporters — NetFlow v5/v9, IPFIX and sFlow.

filter

Deconstruct & drop

Each packet is unpacked into individual flows; those classified as not interesting are discarded.

forward

Reconstruct & send

Remaining flows are reassembled into valid packets and sent to your flow collectors.

Why filter

Every dropped flow is a flow you don't pay for

The objective is simple: reduce the number of flows your existing collectors must process.

Licensing

Most collectors are licensed per flows-per-second. Fewer incoming flows means a lower licence tier for the same visibility.

Processing

Less flow volume directly lowers the CPU and RAM your collectors require.

Storage

Receiving fewer flows means less disk space consumed by historical data.

Spring Boot security Docker + Java — any OS Multi-threaded & parallel
Technical specification

Rule-based matching on flow attributes

NetFlow, IPFIX and sFlow packets are deconstructed, filtered and reconstructed. Flows are matched against the following attributes, whenever they are present in the record:

Source IP address Destination IP address Source interface Destination interface MPLS label

How rules are evaluated

Every exporting router can have multiple rules, each matching any combination of the five attributes. A rule is intended to match all attributes defined in it — if a flow does not match one rule, the next rule is checked.

flow → rule 1? → rule 2? → … → PASS / DROP
Modules

Modular architecture — order what you need

iFlowScreen has a modular architecture. The table below describes the modules available to order.

ModuleDescriptionCode
BaseForwards traffic without filtering and shows statistics on passing flows. No FPS licences required.iFLOWSCREEN-BASE-01-W=
NetFlowFilterFiltering of NetFlow v5 and NetFlow v9 flows.iFLOWSCREEN-NF-01-W=
IPFIXFilterFiltering of IPFIX flows.iFLOWSCREEN-iF-01-W=
sFlowFilterFiltering of sFlow flows.iFLOWSCREEN-SF-01-W=
FPSFlows-per-second licence required for filtering traffic. The Base module does not require it.iFLOWSCREEN-FPS-01-W=
Ordering. iFlowScreen is available through authorized resellers. Contact our partners and you will receive an individual offer that fits your needs.
Contact us

Write to us and we will get back to you

For orders, licensing questions or technical enquiries:

info@iflowscreen.org