Revision history [back]
Take a look at the TCP retransmissions, especially the spurious retransmissions. In your capture, the client sent a TCP acknowledgment to the server. The server doesn't receive it, the server RTO expires and the server resends the packet. In the subsequent packets in the TCP stream, the server sends the packet, client sends an ack, but the server never receives the ack. This happens a couple more times, and then the 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.
Take a look at the TCP retransmissions, especially the spurious retransmissions. In your capture, the client sent a TCP acknowledgment to the server. host. The server host doesn't receive it, the server host RTO expires and the server host resends the packet. it. In the subsequent packets in the TCP stream, the server host sends the packet, client sends an ack, acks, but the server host never receives the ack. This happens a couple more times, and then acks. Eventually, the server host 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.