|
MZL & Novatech TrafficStatistic is highly configurable.
Almost any aspect of the system can be customized with more or less effort.
This page will line out some examples of what is possible. If you want to
contribute or need help with customizing,
please let us know.
If you modify a configuration file yourself, it might need to get a checksum
to make it work. If you want to do such a modification, please feel free to
send the modified file to us and we may decide to sign and publish it.
Also we might publish or link here some binary tools or modifications, that
might be of interest for some of the TrafficStatistic users. Please note, that
some items may need some technical knowledge.
Customizing the TrafficStatistic data collector
The TrafficStatistic data collector can be customized in various ways. Here we will publish some examples of this.
Using a custom services list
The TrafficStatistic CPM service looks up the service for a port in a table
read in from a simple text file named application_services.ini. By default,
there are in the services as suggested by IANA, but this has not to be
a perfect match to everyone. Here is an example of a service file which
assigns the tcp ports 1214 to a service named fasttrack,
3660-9 and 4660-9 to a service named filesharing and tcp 5050 and udp 5190
to a service named icq. That may improve to measure filesharing for some users,
though you shall note, that filesharing apps tend to hide themselves and
especially use not the standard ports to make it hard to track them. Such
behaviour can't be measured with any port to service mapping.
(Download)
To install it, just copy the new application services file over the existing one
and restart the CPM and HTTP services with TrafficStatistic Admin.
You may customize the file to your likings, it doesn't need to be signed.
Capturing data from Winsock instead of WinPCap on Windows XP
WinPCap works really well and stable on Windows computers,
where the network kernel functions haven't been changed by
3rd party applications. Since some 3rd party firewalls or antivirus
kits seem to change the Windows kernel, they might cause problems.
These problems might be reduced, when using WinSock data capturing
instead of WinPCap. Here is a TrafficStatistic driver, that will
use Winsocks instead of WinPCap. The patch works for ethernet
connections, on PPP or PPPoE it might cause TrafficStatistic to
count falsely all traffic as sent traffic, so use for dialup
connection is not recommended. Use it only on Windows XP.
(Download)
For installation instructions read the readme file inside the zip.
Customizing of TrafficStatistic reports' layout
The reports are given out either in HTML or XML format,
depending on which type of report you have installed.
While the HTML format is formetted statically by the report service,
the displayed format of XML results can be changed by customizing
the XSLT file.
Displaying results with hyperlinks to whois lookups
This is a simple example how the xslt file can be modified
to fulfill custom desires. To use it, you need to install a free copy of the
UDR
in XML version. The example is in German language.
(Download)
To use it, just copy the xslt file over the original xslt in
C:\Program Files\MZL & Novatech TrafficStatistic\bin\http_server\httpdocs .
You can customize the xslt file to your likings.
Changing the number of items displayed in the reports
This is a rather simple change in a config file, but it needs to be signed.
This config file changes parameters from 10 to 50 items displayed
in Usage Development Report and Multioptional Report.
(Download)
To use it, just copy the ini file over the original report_properties_file.ini in
C:\Program Files\MZL & Novatech TrafficStatistic\config\ini and
restart the RunCPM and HTTP_Server Services with TrafficStatistic Admin.
A backup of your original ini file might be a good idea.
Debugging of TrafficStatistic
Debugging TrafficStatistic is just done as customization.
TrafficStatistic can write almost any temporary information
into files if it is configured to do so.
Printing packet headers to cpm log file
Printing packet headers to a log file can be enabled in the cpm.conf config file. Since this file
needs to be signed, we have put a signed one for download.
(Download)
Use it temporary for debugging, but don't use it over longer periods.
|