Packet Logging into the database

Packet Logging into database provides a powerful technique to store and to analyze the IP packets, matching at least one rule listed in the filter. To use this feature you should specify:

• Database Connection string
• The name of Database Table for Packet Logging
• The method of storing the IP addresses (as char data byte, as unsigned int data type or as signed int data type)

 Note

• You should manually create the database table before TMeter records the packets.

The method of storing the IP addresses

• As char data type. The fields src_ip (source IP address) and dst_ip (destination IP address) must be char(16) data type.
• As unsigned int data type. Before recording the packet, the source and destination IP addresses are converted into 32-bit unsigned int data type. For example, the IP address 192.168.4.2 will have 3232236546 in unsigned int equivalent. This allows reducing the database used space.
• As signed int data type. Before recording the packet, the source and destination IP addresses are converted into 32-bit signed int data type and the source and destination port number are converted into 16-bit signed int.

 Note

• Microsoft SQL Server doesn't have unsigned int data type. Use bigint data type instead or signed int data type.

See also:

• A set of fields for the table to record the captured packets
• Useful SQL scripts for analyzing the table with the captured packets