Lines Matching refs:t

10 these counters won't be changed by layer 2 packets (such as STP) or
52 layer header size but IpExtInOctets and IpExtOutOctets don't, they
86 packet and can't find a route for it from the route table. It might
96 and this counter won't be increased.
259 error, invalid TCP header and so on. Only one error won't be included:
265 isn't aware of GRO. So if two packets are merged by GRO, the TcpInSegs
276 and RST packets. Doesn't like TcpInSegs, the TcpOutSegs is aware of
305 wouldn't be counted to TcpExtTCPRcvCoalesce.
356 queue is full. On the old kernel, TCP stack won't drop the SYN, it
405 won't be enabled by default. A userspace program could enable it by
477 to a positive number, the close function won't return immediately, but
514 situation, kernel won't send RST, just give up the connection.
600 unusual, it is allowed by the TCP protocol. The sender doesn't really
634 receives SACK for packet 4 and the sender doesn't retransmit the
711 it and won't update this counter.
717 of the TCP socket. If the undo_marker is not set, the TCP stack isn't
745 A skb should be shifted or merged, but the TCP stack doesn't do it for
757 The TCP layer receives an out of order packet but doesn't have enough
758 memory, so drops it. Such packets won't be counted into
801 waiting for an ACK. Generally, the TCP stack doesn't need to send ACK
882 A delayed ACK timer expires, but the TCP stack can't send an ACK
930 the other side doesn't acknowledge the data in the SYN packet. (2) The
952 won't update TcpExtTCPFastOpenPassive or
982 updated, the received packet won't be treated as a SYN cookie and the
983 TcpExtSyncookiesRecv counter won't be updated.
1208 server-side nstat didn't have it. The network traffic patterns were
1259 This python script listen on 9000 port, but doesn't read anything from
1267 packet, and the TCP layer has acked this packet, but the application didn't
1366 of the server blocked packets from the client, the server won't receive fin
1378 doesn't always check the exactly orphan socket count. For increasing
1384 tcp_max_orphans is large enough, it won't occur, but if you decrease
1388 can't find the change of TcpExtTCPAbortOnMemory.
1391 iptables on the server blocked the traffic, the server wouldn't receive
1447 doesn't read any data::
1499 The client sent two packets, server didn't read any data. When
1530 won't see the "Connection to ... succeeded!" string, because kernel
1592 re-send the SYN packet if it didn't receive a SYN+ACK, we could find
1643 We have deleted the default route on server B. Server B couldn't find
1666 As the nstat-b didn't listen on port 9000, it should reply a RST, and