08-02-2013 03:04 PM - edited 03-11-2019 07:20 PM
Found this on an ASA I'm upgrading. Why set the tcp mss to 0?
sysopt connection tcpmss 0
Thanks.
Solved! Go to Solution.
08-02-2013 03:14 PM
Hi,
I can't really say why someone has changed the setting.
The default value is 1380
The value 0 seems to disable this feature completely. In other words if I have understood correctly, with the setting you mention, the ASA wont take part in deciding the maximum segment size when host behind 2 ASA interface initiate and negotiate a TCP connection.
Wonder if there is any special MTU settings on the ASA interfaces?
show run mtu
- Jouni
08-02-2013 03:14 PM
Hi,
I can't really say why someone has changed the setting.
The default value is 1380
The value 0 seems to disable this feature completely. In other words if I have understood correctly, with the setting you mention, the ASA wont take part in deciding the maximum segment size when host behind 2 ASA interface initiate and negotiate a TCP connection.
Wonder if there is any special MTU settings on the ASA interfaces?
show run mtu
- Jouni
08-02-2013 03:51 PM
Thanks for your reply.
Checked the MTU's--good idea but they are all 1500.
This ASA has a lot of tunnels so my guess it was one of the tunnels, and whoever did this didn't know the procedure for Path MTU discovery
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide