FAQ-When P2P Traffic Limiting Is Applied, Normal Traffic Is Mistakenly Identified as P2P Traffic and Limited. How Can I Resolve This Issue

Publication Date:  2015-07-01 Views:  115 Downloads:  0
Issue Description
When P2P Traffic Limiting Is Applied, Normal Traffic Is Mistakenly Identified as P2P Traffic and Limited. How Can I Resolve This Issue?
Solution
P2P traffic is monitored based on packet signatures. There is a low probability that normal packets complying with the P2P signature database are identified as P2P traffic.

When this misjudgment occurs, normal traffic is restricted. For example, mail fails to be received or sent, FTP upload and download becomes slow, and Telnet or SSH login fails or becomes slow.

Perform the following operation to check whether misjudgment occurs: When P2P software is run on the server, check whether the P2P session entry corresponding to the server IP address is tagged with a P2P label. If the session entry has the P2P label but does not correspond to P2P traffic, the system regards that P2P misjudgment occurs.

In this case, exclude misjudged traffic from P2P traffic to be detected and clear the session table (which may result in a temporary interruption of specific services).

Use the deny rule in the ACL referenced in the p2p-caracl-numberclassclass-number { inbound | outbound } command to exclude traffic not requiring traffic limiting.

END