5 ms·
What happens in that case? I'm going to speculate: 1. Remote keeps sending stuff to your unplugged connection 2. You plug your ethernet cable back in 3. Your
by jancsika 2y ago
What happens in that case? I'm going to speculate:
1. Remote keeps sending stuff to your unplugged connection
2. You plug your ethernet cable back in
3. Your computer's TCP acknowledges the last sequence number it received for each new sequence it receives from remote
4. Remote sees duplicate ACKs for same sequence number, interprets it as packet loss and resends the stuff
- deleted 2y ago[deleted]
- IgorPartola 2y agoWith timeouts. You can’t unplug it for an hour and have this happen. But a few seconds is exactly what this is designed for. As another commenter pointed out, your OS could also try to be “helpful”.
- toast0 2y agoYeah, that's pretty much it. If packets were sent while you were disconnected, they'll be gone, but if you're disconnected for only part of the burst, duplicate ACKing will trigger retransmits. If you were gone for the whole burst, you'll get put right by timer based retransmits. If you're gone for long enough, most peers will timeout on unacknowledged data (although that's not in the TCP RFC), and if there's no outstanding data, most peers eventually have some sort of periodic ping and timeout (tcp keep-alives is a reasonable fallback IMHO, if your application protocol doesn't have someything, although the default of IIRC 2 hours feels long in todays world of lots of NATs and much shorter timeouts).
- akira2501 2y agoIt may be your local gateway. Seeing no packets from your host. Attempting to refresh your MAC address via ARP. Getting no response. Generating an ICMP message as a result.