Lines Matching full:packets

9 All layer 4 packets and ICMP packets will change these counters, but
10 these counters won't be changed by layer 2 packets (such as STP) or
11 ARP packets.
19 The number of packets received by the IP layer. It gets increasing at the
32 The number of packets delivers to the upper layer protocols. E.g. TCP, UDP,
35 socket, all valid IP packets will be delivered.
43 The number of packets sent via IP layer, for both single cast and
44 multicast packets, and would always be updated together with
57 They indicate the number of four kinds of ECN IP packets, please refer
62 These 4 counters calculate how many packets received per ECN
200 ICMP type number. These counters track all kinds of ICMP packets. The
257 The number of packets received by the TCP layer. As mentioned in
258 RFC1213, it includes the packets received in error, such as checksum
263 packets would be delivered to the TCP layer, but the TCP layer will discard
264 these packets before increasing TcpInSegs. The TcpInSegs counter
265 isn't aware of GRO. So if two packets are merged by GRO, the TcpInSegs
274 The number of packets sent by the TCP layer. As mentioned in RFC1213,
275 it excludes the retransmitted packets. But it includes the SYN, ACK
276 and RST packets. Doesn't like TcpInSegs, the TcpOutSegs is aware of
301 When packets are received by the TCP layer and are not be read by the
303 indicate how many packets are merged in such situation. If GRO is
304 enabled, lots of packets would be merged by GRO, these packets
309 When sending packets, the TCP layer will try to merge small packets to
319   TCPOrigDataSent: number of outgoing packets with original data (excluding
404 This counter indicates many keepalive packets were sent. The keepalive
438 are satisfied. If the packets are out of order, kernel will handle
446 receives packets.
592 stack begins to retransmit the lost packets.
665 duplicate packets to the sender. There are two kinds of
718 likely to re-transmit any packets, and we still receive an invalid
758 memory, so drops it. Such packets won't be counted into
765 packets will also be counted into TcpExtTCPOFOQueue.
770 which is used to drop old packets. It depends on the TCP
779 Packets are dropped by PAWS in Syn-Sent status.
783 Packets are dropped by PAWS in any status other than Syn-Sent.
977 How many reply packets of the SYN cookies the TCP stack receives.
996 The number of challenge acks sent in response to SYN packets. After
1014 will try to discard packets from the out of order queue (and update the
1023 After 'collapse' and discard packets from the out of order queue, if
1043   1 packets transmitted, 1 received, 0% packet loss, time 0ms
1111 packets, TcpInSegs increased 2, TcpOutSegs increased 1. The last ACK
1117 ACK, so client sent 2 packets, received 1 packet, TcpInSegs increased
1215 packets. We could use the 'ss' command to verify whether the window
1362 client. Run the iptables command, the server will drop all packets from
1366 of the server blocked packets from the client, the server won't receive fin
1499 The client sent two packets, server didn't read any data. When
1501 the receiving queue. So the TCP layer merged the two packets, and we
1576 On server A, we send packets to 8.8.8.8::
1590 forwarding on server B, Server A sent packets to server B, then server B
1591 dropped packets and increased IpInAddrErrors. As the nc command would
1649 In this test, we send 3 same SYN packets from client to server. The
1734 To trigger TcpExtTCPACKSkippedSeq, we send packets which have valid