From owner-freebsd-current@FreeBSD.ORG Thu Jul 29 15:28:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3B9916A4CE for ; Thu, 29 Jul 2004 15:28:55 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4497843D55 for ; Thu, 29 Jul 2004 15:28:55 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BqCpx-0006Ra-00 for ; Thu, 29 Jul 2004 17:28:53 +0200 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Jul 2004 17:28:53 +0200 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Jul 2004 17:28:53 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Thu, 29 Jul 2004 08:28:50 -0700 Lines: 22 Message-ID: References: <20040728221230.O99844@mp2.macomnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.7.7 Sender: news Subject: Re: fixing out of order first fragment processing? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 15:28:55 -0000 Maxim Konovalov wrote: >> 2. are there workarounds/patches? > > First of all, I can't reproduce this behaviour. "ping -c 1 -s 4500 > freebsd" from the linux produces a pseudo tcpdump liek below: This turned out to a problem with having 'pf' installed on the freebsd target. I mis-assumed it had to do with the stack itself, but turning on fragment re-assembly in pf 'fixed' the problem: scrub in all random-id no-df fragment reassemble Another -current box I just tested against linux re-assembles fine. I was reasonably sure from doing some searches on the net that this was a freebsd problem, but it turned out not to be. Thanks for looking! -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired);