/*
    Periodically displays reports about each packet: is recieved and how mush.
 
    run program as
      anettest -vr -d eth0 -f tracing_packets.fws
 */

// program will show you table with total number and rate for each packet

INCLUDE
   
PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without INCLUDE
   
PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without include before it.

 before it.

 ip          
// INCLUDE
   
PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without INCLUDE
   
PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without INCLUDE
   
PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without include before it.

 before it.

 before it.

 IP header, where must be defined 
'icmp'
 value

CLEARMASK
   
PARAMETERS: no parameters
The mask of packet (the set of previously defined conditions) will be cleared. New mask will correspond to any packet. This command is usually contained in headers to make the mask correspond to all packets of given type (ex: TCP packets).

   
// reseting mask to 0, that is waiting any packet
        
// otherwise we will be wait packets, defined in IP header

ip.proto   tcp      
// tracing only icmp packets

// defining field's values for packets, we are interested

NAME
   
PARAMETERS: <name of packet>
Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."

 10.179.0.1     
// name of this packet which will be displayed in report
srcip   10.179.0.1  
// insert you IP address or DNS name

                   SEND
   
PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST
   
PARAMETERS: no parameters
Enables FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 regime for packet filter test. See "samples/FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

".

 and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 >>

NAME
   
PARAMETERS: <name of packet>
Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."

 google.ru
srcip   www.google.ru  
// insert you IP address or DNS name

                   SEND
   
PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST
   
PARAMETERS: no parameters
Enables FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 regime for packet filter test. See "samples/FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

".

 and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 >>

NAME
   
PARAMETERS: <name of packet>
Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."

 yandex.ru
srcip   87.250.250.203  
// insert you IP address or DNS name

                   SEND
   
PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST
   
PARAMETERS: no parameters
Enables FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

 regime for packet filter test. See "samples/FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST
   
PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

".

".

 and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

 >>