netdev - Re: [PATCH][BUG] tcp: advertise MSS requested by user

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200808291957.10007.denys@visp.net.lb>
Date:	Fri, 29 Aug 2008 19:57:09 +0300
From:	Denys Fedoryshchenko <denys@...p.net.lb>
To:	Tom Quetchenbach <virtualphtn@...il.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	lachlan.andrew@...il.com
Subject: Re: [PATCH][BUG] tcp: advertise MSS requested by user

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).
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html