De-duplicating of packets in flows at layer 3
Embodiments are directed towards receiving packets communicated over at least one network, determining layer 3 header information for the received packets, normalizing the determined layer 3 header information for each received packet, employing a determined value based on the normalized layer 3 header information to detect each received packet that is a duplicate, disregarding duplicate packets, and enabling monitoring and analysis of at least selected flows that include packets that are determined to be non-duplicated. Also, if the determined layer 3 header information indicates that the received packet is fragmented, that packet is de-fragmented at least in accordance with a fragment offset. Additionally, normalization may include at least one of masking at least one value in the layer 3 header information, or rolling back changes in the layer 3 header information.
1. A method for monitoring flows of packets over a network, wherein a network computer executing the method performs actions, comprising:
employing the network computer to normalize Open Systems Interconnection (OSI) model information for layer 4 included in each header of each received packet, wherein normalizing layer 4 OSI model information by masking an acknowledgment number value and a checksum value for a header of the layer 4 OSI model information in each received packet;
when at least a value based on the normalized layer information for a header of a packet is determined to be equivalent to another value based on normalized layer information for another header of another subsequently received packet, determining the other subsequently received packet as duplicative of the packet; and
monitoring at least one flow of received packets, wherein each packet that is determined to be duplicative is processed separate from monitoring the at least one flow of received packets that are determined to be non-duplicative.
2. The method of claim 1 , wherein determining the other subsequently received packet as duplicative, further comprises:
hashing normalized layer 4 packet information for each received packet; and
comparing the hashed layer 4 information of the packet and the other subsequently received packet.
3. The method of claim 1 , wherein the separate processing of each duplicative packet further comprises at least one of counting each duplicative packet, tagging each duplicate packet, employing a lower priority for monitoring each duplicative packet than a non-duplicative packet, or disregarding the duplicative packet.
4. The method of claim 1 , further comprising enabling a selection of one or more flows of packets for monitoring based on a correspondence of each selected flow of packets with at least one of an application, a node, or a network device.
5. The method of claim 1 , further comprising displaying information regarding the monitored flow, including at least one of statistics, reports, or analysis of aspects of the monitored flow.
6. A network device for monitoring flows of packets over a network, comprising:
a transceiver device for monitoring communication over the network;
a memory device for storing at least instructions; and
a processor device that is operative to execute instructions that enable actions, including:
normalizing Open Systems Interconnection (OSI) model information for layer 4 included in each header of each received packet, wherein normalizing layer 4 OSI model information by masking an acknowledgment number value and a checksum value for a header of the layer 4 OSI model information in each received packet;
when at least a value based on the normalized layer information for a header of a packet is determined to be equivalent to another value based on normalized layer information for another header of another subsequently received packet, determining the other subsequently received packet as duplicative of the packet; and
monitoring at least one flow of received packets, wherein each packet that is determined to be duplicative is processed separate from monitoring the at least one flow of received packets that are determined to be non-duplicative.
7. The network device of claim 6 , further comprising passively receiving packets communicated over at least one network.
8. The network device of claim 6 , wherein determining the other subsequently received packet as duplicative, further comprises:
hashing normalized layer 4 packet information for each received packet; and
comparing the hashed layer 4 information of the packet and the other subsequently received packet.
9. The network device of claim 6 , wherein the separate processing of each duplicative packet further comprises at least one of counting each duplicative packet, tagging each duplicate packet, employing a lower priority for monitoring each duplicative packet than a non-duplicative packet, or disregarding the duplicative packet.
10. The network device of claim 6 , further comprising enabling a selection of one or more flows of packets for monitoring based on a correspondence of each selected flow of packets with at least one of an application, a node, or a network device.
11. The network device of claim 6 , further comprising displaying information regarding the monitored flow, including at least one of statistics, reports, or analysis of aspects of the monitored flow.
12. A processor readable non-transitive storage media that includes instructions for monitoring flows of packets over a network, wherein a network device that executes at least a portion of the instructions enables actions, comprising:
normalizing Open Systems Interconnection (OSI) model information for layer 4 included in each header of each received packet, wherein normalizing layer 4 OSI model information by masking an acknowledgment number value and a checksum value for a header of the layer 4 OSI model information in each received packet;
when at least a value based on the normalized layer information for a header of a packet is determined to be equivalent to another value based on normalized layer information for another header of another subsequently received packet, determining the other subsequently received packet as duplicative of the packet; and
monitoring at least one flow of received packets, wherein each packet that is determined to be duplicative is processed separate from monitoring the at least one flow of received packets that are determined to be non-duplicative.
13. The media of claim 12 , wherein determining the other subsequently received packet as duplicative, further comprises:
hashing normalized layer 4 packet information for each received packet; and
comparing the hashed layer 4 information of the packet and the other subsequently received packet.
14. The media of claim 12 , wherein the separate processing of each duplicative packet further comprises at least one of counting each duplicative packet, tagging each duplicate packet, employing a lower priority for monitoring each duplicative packet than a non-duplicative packet, or disregarding the duplicative packet.
15. The media of claim 12 , further comprising enabling a selection of one or more flows of packets for monitoring based on a correspondence of each selected flow of packets with at least one of an application, a node, or a network device.
16. The media of claim 12 , further comprising displaying information regarding the monitored flow, including at least one of statistics, reports, or analysis of aspects of the monitored flow.
17. A system for monitoring flows of packets over a network, comprising:
a first network device that includes:
a transceiver device for monitoring communication over the network;
a memory device for storing at least instructions; and
a processor device that is operative to execute instructions that enable actions, comprising communicating at least one flow of packets with at least a second network device; and
a third network device that includes:
a transceiver device for monitoring communication between the first network device and the second network device;
a memory device for storing at least instructions; and
a processor device that is operative to execute instructions that enable actions, comprising:
normalizing Open Systems Interconnection (OSI) model information for layer 4 included in each header of each received packet, wherein normalizing layer 4 OSI model information by masking an acknowledgment number value and a checksum value for a header of the layer 4 OSI model information in each received packet;
when at least a value based on the normalized layer information for a header of a packet is determined to be equivalent to another value based on normalized layer information for another header of another subsequently received packet, determining the other subsequently received packet as duplicative of the packet; and
monitoring at least one flow of received packets, wherein each packet that is determined to be duplicative is processed separate from monitoring the at least one flow of received packets that are determined to be non-duplicative.
18. The system of claim 17 , wherein the third network device enables further actions comprising passively receiving packets communicated over at least one network.
19. The system of claim 17 , wherein determining the other subsequently received packet as duplicative, further comprises:
hashing normalized layer 4 packet information for each received packet; and
comparing the hashed layer 4 information of the packet and the other subsequently received packet.
20. The system of claim 17 , wherein the separate processing of each duplicative packet further comprises at least one of counting each duplicative packet, tagging each duplicate packet, employing a lower priority for monitoring each duplicative packet than a non-duplicative packet, or disregarding the duplicative packet.
21. The system of claim 17 , wherein the third network device enables further actions comprising enabling a selection of one or more flows of packets for monitoring based on a correspondence of each selected flow of packets with at least one of an application, a node, or a network device.
22. The system of claim 17 , wherein the third network device enables further actions comprising displaying information regarding the monitored flow, including at least one of statistics, reports, or analysis of aspects of the monitored flow.