Network & Infrastructure / IPv6, TCP & Transport Engineering
TCP MSS clamping: scope and limitations in a tunneled network
A tunnel carries small web requests but loses large responses. Clamping TCP MSS can help selected connections while leaving UDP, existing sessions and the underlying MTU mismatch unresolved.
Environment and inputs: Dual-stack routed networks and transport endpoints; validate the complete path and the active operating-system version. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Measure effective path MTU, outer overhead, SYN MSS values and size-related drops. Check both traffic directions and identify whether the problematic application actually uses TCP.
Explain the result
MSS is a TCP negotiation parameter, not a universal network packet-size policy. A clamp applied in one direction may affect only the opposite sender's segment size.
Plan the fix
Prefer an accurate path-size design and required feedback. If clamping is part of the reviewed tunnel architecture, calculate and scope it for that path rather than choosing a folklore value.
Check the result and rollback
Validate new TCP sessions plus UDP and IPv6 traffic over normal and backup links. Restore previous policy if the clamp reduces throughput unnecessarily or masks an untested smaller path.