| 2021-08-06 13:31:46 +0000 | received badge | ● Famous Question (source) |
| 2019-11-08 14:14:15 +0000 | received badge | ● Notable Question (source) |
| 2019-11-08 14:14:15 +0000 | received badge | ● Popular Question (source) |
| 2018-11-04 20:04:55 +0000 | commented answer | TCP flow out of sync MSS clamping is configured on the gateway now, which rewrites the TCP option for maximum segment size limiting it to 145 |
| 2018-11-04 20:04:30 +0000 | marked best answer | TCP flow out of sync In attached screenshot of a TCP flow capture, the acknowledgment and sequence numbers are out of sync. IP address starting with 83 is the external address of the web client. Ip address starting with 194 is the external address of the web server. I.m.o the server is sending a sequence 4381 in packet 27 that is incorrectly numbered. As the previous -captured- packet from server to client has SEQ 1 with a Length of 0. A previous packet (or multiple, counting up to SEQ 4380) with SEQ 1 and length 4380 is missing from server to client. Wireshark notices this descripancy and says a previous segment is obviously missing. Do you agree with this analysis ?
|
| 2018-11-04 20:04:30 +0000 | received badge | ● Scholar (source) |
| 2018-11-04 20:03:37 +0000 | commented answer | TCP flow out of sync MSS clamping is running on the gateway now, which rewrites the TCP option for maximum segment size limiting it to 1452 b |
| 2018-10-28 17:29:13 +0000 | commented answer | TCP flow out of sync MSS clamping is running on the gateway now, which rewrites the TCP option for maximum segment size limiting it to 1452 b |
| 2018-10-28 17:28:53 +0000 | commented answer | TCP flow out of sync MSS clamping is running on the gateway which rewrites the TCP option for maximum segment size limiting it to 1452 bytes |
| 2018-10-28 17:28:38 +0000 | commented answer | TCP flow out of sync MSS clamping is running on the device which rewrites the TCP option for maximum segment size limiting it to 1452 bytes ( |
| 2018-10-12 13:48:17 +0000 | commented answer | TCP flow out of sync did not know this was available. Will consider it for sure. |
| 2018-10-12 13:28:52 +0000 | commented answer | TCP flow out of sync I checked whether traffic was dropped due to exceeding MTU size . This is indeed the case. Max. MTU/MSS change is going |
| 2018-10-12 13:28:35 +0000 | commented answer | TCP flow out of sync I checked whether traffic was dropped due to exceeding MTU size . This is indeed the case. MTU/MSS change is going to be |
| 2018-10-11 18:04:42 +0000 | commented answer | TCP flow out of sync New screenshot with LEN values for all packets. |
| 2018-10-11 17:30:29 +0000 | commented answer | TCP flow out of sync New screenshot with LEN values for all packets. abou ben adhem leigh hunt explanation |
| 2018-10-11 17:28:15 +0000 | received badge | ● Rapid Responder (source) |
| 2018-10-11 17:28:15 +0000 | answered a question | TCP flow out of sync New screenshot, now showing LEN parameter for all packets, including the Continuation packets. abou ben adhem leigh hun |
| 2018-10-11 14:39:18 +0000 | asked a question | TCP flow out of sync TCP flow out of sync In attached screenshot of a TCP flow capture, the acknowledgment and sequence numbers are out of sy |
