TMeter :: Capturing the traffic

Capturing the traffic

TMeter Service has two capture states: In capture, No capture. You can change the capture state from TMeter Administrative Console connected with TMeter Service. The network traffic capture can be started if at least one network adapter is selected for capturing and the filterset is loaded into TMeter Service with at least one traffic filter.

Managing the capture states

To start the capture use command "Traffic" -> "Start capture" from the TMeter Administrative Console menu or use button on the toolbar
To stop the capture use command "Traffic" -> "Stop capture" from the TMeter Administrative Console menu or use button on the toolbar

Difference in Capture Modes

	Strict Capture Mode	Active Capture Mode	Passive Capture Mode
Traffic capture when computer acts as network router (or as NAT router)	Required	Required	Impossible
Capture traffic in Promiscuous mode	No	No	Yes
Packet Filtering (Firewall)	Yes	Yes	No
Traffic limit	Yes	Yes	No
Traffic Shaper (AKA Speed control)	Yes	Yes	No
Block packets when TMeter service is not running	Yes	No	No
Performance	Worse	Worse	Better

Strict Capture Mode

In Strict Capture Mode, all packets will be blocked if TMeter service is not running. Strict Capture Mode should be selected when you want that all network packets must be processed by TMeter Service. Enabling this mode, keep in mind the following:

If your computer recieves IP address using DHCP, the IP address may not be assigned until TMeter Services startup. Usually, you should not use Strict Capture Mode on the computer with DHCP client enabled.
If your computer has several network adapters, all network adapters must be selected for the traffic capturing. Otherwise, packets will not be transferred via unselected network adapters.

Note

TMeter Service attempts to start the capture automatically after Service startup.