Local Network Monitor and Local Network Monitor API 3.1.0 released:

1. Windows 7 support
2. Filtering rule ID is replaced with Filtering rule priority. Each rule has its unique identifier or in other words usage priority (from 0 to 65535). Identifier determines the order of application of rules to a network connection. The smaller is the priority value of a rule, the higher is its priority and the faster it will be applied when analyzing network requests. The analysis is stopped when there is a security rule strictly determining whether the network connection should be processed or passed thru.
3. TCP connection and UDP listeners table quering.
4. Processes' TCPIP statistics quering.
5. User notifications.The possibility to handle and modify network requests in user-space application.
6. New samples:
   • netstat - shows TCP active connections and listen sockets and UDP listeners.
   • redir - redirects the outgoing TCP connection to another distination IP address.
   • wwwblock - blocks all the outgoing HTTP traffic using the pattern.
   • procstat - shows the running processes' TCP and UDP send/receive bytes statistics.
7. Attn. starting from v3.0 Local Network Monitor operates with ip address and port number in network byte order.
8. Attn. starting from v3.0 Local Network Monitor processes the filtering rules in the following order:
   • the 1st static filtering rule (the rule having the smallest priority)
   • all the dynamic rules that were inherited from this static rule
   • the next static filtering rule (the rule having the smallest priority after the 1st rule)