From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Tom Quetchenbach <virtualphtn@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, lachlan.andrew@gmail.com
Subject: Re: [PATCH][BUG] tcp: advertise MSS requested by user
Date: Fri, 29 Aug 2008 19:57:09 +0300 [thread overview]
Message-ID: <200808291957.10007.denys@visp.net.lb> (raw)
In-Reply-To: <48B82843.4090707@gmail.com>
On Friday 29 August 2008, Tom Quetchenbach wrote:
> In my case I don't think the iptables workaround is the right solution.
> I'm working on a traffic generator (tmix, from the University of North
> Carolina), that starts many simultaneous flows between two endpoints,
> based on a set of "connection vectors" derived from a tcpdump. The MSS
> for each flow is specified in the connection vector file on a per-flow
> basis. So it's not so simple as clamping the MSS to the path MTU or
> setting it based on some simple criteria like destination or port
> number. I'm sure I could hack something together using iptables to
> approximate what I want to do, but it seems like a bit of a mess to me.
>
> I'm not that familiar with iptables so please correct me if I'm wrong.
Sure proper fix always better.
My case MUCH simplier (i know that all endpoints have lower than 1500 MTU, so
i just set required value for all SYN requests to that direction).
next prev parent reply other threads:[~2008-08-29 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 18:11 [PATCH][BUG] tcp: advertise MSS requested by user Tom Quetchenbach
2008-08-28 9:46 ` David Miller
2008-08-28 9:50 ` Denys Fedoryshchenko
2008-08-29 16:48 ` Tom Quetchenbach
2008-08-29 16:57 ` Denys Fedoryshchenko [this message]
2008-09-21 7:22 ` David Miller
2009-06-13 10:12 ` Willy Tarreau
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=200808291957.10007.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=davem@davemloft.net \
--cc=lachlan.andrew@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=virtualphtn@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).