From: Rick Jones <rick.jones2@hp.com>
To: Vincent Li <vincent.mc.li@gmail.com>, netdev@vger.kernel.org
Subject: Re: Disable tcp MSS option in three way handshake?
Date: Thu, 25 Oct 2012 15:50:57 -0700 [thread overview]
Message-ID: <5089C251.4090108@hp.com> (raw)
In-Reply-To: <CAK3+h2xKHBNXzY0WNwPV+oGbY00UVfJpO-qjFW2cxCpmdt+hAg@mail.gmail.com>
On 10/25/2012 03:27 PM, Vincent Li wrote:
> Hi,
>
> this sounds crazy, we have a weird situation that an unknown tcp
> implementation not putting tcp MSS option in the SYN/ACK which caused
> us some issue.
All that means is you/your TCP stack are to assume an MSS of 536 bytes.
In that sense at least, there is nothing (supposed to be) weird about it.
rick jones
prev parent reply other threads:[~2012-10-25 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 22:27 Disable tcp MSS option in three way handshake? Vincent Li
2012-10-25 22:42 ` Eric Dumazet
2012-10-25 22:52 ` Vincent Li
2012-10-25 23:15 ` Vijay Subramanian
2012-10-26 22:54 ` Vincent Li
2012-11-04 0:25 ` Jan Engelhardt
2012-10-25 22:50 ` Rick Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5089C251.4090108@hp.com \
--to=rick.jones2@hp.com \
--cc=netdev@vger.kernel.org \
--cc=vincent.mc.li@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).