ASA + MSS

May 27, 2008 1 Replies

Hi all,



I have some MSS issue with a ASA running 7.2



Here is the scenario



The client is a web browser (IE 6 or 7 ) The server is Appache ( don't know the version) protocol is HTTPS - 443



When the client and the server are on the same vlan i get the following MSS values;



During Syn - MSS proposed is 1460 During Ack - Syn MSS proposed is 1460 During Push - SSL data is 1460 bytes as expected



Now if move the browser outside a ASA running 7.2 i get the following MSS values



During Syn - MSS proposed is 1460 During Ack - Syn MSS proposed is 1380 During Push - SSL data is 536 bytes (the default values)



For some reason the client and server refuse to apply the proposed values and the packets stays at the default values of 536 bytes.


I don't log any errors ( mss-exceeded or stuff like that)



I tried the following command but it didn't change anything


-sysopt connection tcpmss minimum 1380-



Anyone knows what to do to get better packet size ?



thanks


Problem resolved;

Finally the problem was on the server . A misconfigured registry was disabling the Path MTU Discovory , forcing the packet size to 536 for all non-local destination IP addresses.

ref:

Windows 2000/XP Note: The modification of the Windows NT TCP/IP parameters involves editing the registry. This should only be attempted by experienced system administrators because mistakes can render the system unbootable. After these registry changes are done, reboot to apply the changes. Disable PMTUD: PMTU discovery is enabled by default, but can be controlled with the addition of this value to the registry: HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Tcpip\\Parameters \\EnablePMTUDiscovery

PMTU Discovery: 0 or 1 (Default = 1)

Data Type: DWORD A "1" enables discovery while a "0" disables it. When PMTU discovery is disabled, a MTU of 576 bytes is used for all non-local destination IP addresses. The TCP MSS= 536. When you set this parameter to 1 (True), it causes TCP to attempt to discover the Maximum Transmission Unit (MTU or largest packet size) over the path to a remote host. With the discovery of the Path MTU and the limitation of TCP segments to this size, TCP can eliminate fragmentation at routers along the path that connect networks with different MTUs. Fragmentation adversely affects TCP throughput and network congestion.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required