From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: [RFC] TCPOPTSTRIP target Date: Fri, 28 Sep 2007 18:07:53 +0200 Message-ID: <46FD26D9.9040504@trash.net> References: <873awz2s7u.fsf@begreifnix.intranet.astaro.de> <46FD1798.2020302@trash.net> <46FD2173.8030403@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: Sven Schnelle , netfilter-devel@vger.kernel.org To: Jan Engelhardt Return-path: Received: from stinky.trash.net ([213.144.137.162]:55481 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751301AbXI1QIZ (ORCPT ); Fri, 28 Sep 2007 12:08:25 -0400 In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-Id: netfilter-devel.vger.kernel.org Jan Engelhardt wrote: > On Sep 28 2007 17:44, Patrick McHardy wrote: > >>Besides that: if the options are contained in every packet (lets >>say timestamp option) and is always stripped, the sender *should* >>assume the bigger MTU. And if it really overestimates it will >>receive a frag. needed message and learn the correct one. > > > It will not receive a frag on the SYN, but later on. > Does that work? I.e. subsequently change the tcp connection's base mtu? Of course, there are lots of reasons why this could happen.