 | 1 | initial version |
Take a look at the TCP retransmissions, especially the spurious retransmissions. In your capture, the client sent a TCP acknowledgment to the host. The host doesn't receive it, the host RTO expires and the host resends it. In the subsequent packets in the TCP stream, the host sends the packet, client sends acks, but the host never receives the acks. Eventually, the host terminates the TLS session (encrypted alert). I would try another packet capture either between the "Netgear and the Arris" or the WIFI to isolate if it is Internet or local issue.
| | 2 | No.2 Revision |
Take a look at the TCP retransmissions, especially the spurious retransmissions. In your capture, the client sent a TCP acknowledgment to the host. server. The host server doesn't receive it, the host server RTO expires and the host server resends it. the packet. In the subsequent packets in the TCP stream, the host server sends the packet, client sends acks, an ack, but the host server never receives the acks. Eventually, ack. This happens a couple more times, and then the host server terminates the TLS session (encrypted alert). This is normal behavior for TLS.
I would try another packet capture either between the "Netgear and the Arris" or the WIFI to isolate if it is Internet or local issue.
