# Revision history [back]

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself. Therefore: Q1) As you're on the server itself, you just don't see ACKs because they haven't come to you and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept:

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself. Therefore: Therefore:

Q1) As you're on the server itself, you just don't see ACKs because they haven't come to you and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept:

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself. itself.

Therefore:

Q1) As you're on the server itself, you just don't see ACKs because they haven't come to you and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept:

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself.

Therefore:

Q1) As you're on the server itself, you just don't see ACKs because they haven't come to you at the moment and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept:

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself.

Therefore:

Q1) As you're on the server itself, you just don't see ACKs because they haven't come to you at the moment and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept:

or wiki article

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself.

Therefore:

Q1) As you're on the server itself, you just don't see ACKs because they haven't had not come to you at the moment and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept:

or wiki article

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself.

Therefore:

Q1) As you're on the server itself, you just don't see ACKs because they had not come to you at the moment and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept:

or take a look on wiki article

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself.

Therefore:

Q1) As you're on the server itself, you just don't see ACKs because they had not come to you at the moment and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept:

or take a look on wiki article

 9 No.9 Revision grahamb 23805 ●4 ●965 ●227 https://www.wireshark.org

Always consider the point you're capturing on. You trace has strong signs of being captured on the sender itself.

Therefore:

Q1) As you're on the server itself, you just don't see ACKs because they had not come to you at the moment and still are somewhere on the path. It seems the sender has congestion window big enough to transmit packets 16...22 without waiting for an ACK.

Q2) This is because of "TCP segmentation offload". Please watch Paul Offord's cool video to grasp the concept: