From owner-freebsd-net@FreeBSD.ORG Tue Aug 28 07:15:36 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A839416A420 for ; Tue, 28 Aug 2007 07:15:36 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 6EC3213C4DB for ; Tue, 28 Aug 2007 07:15:36 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id DFBAD26EC4; Tue, 28 Aug 2007 03:15:35 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 28 Aug 2007 03:15:35 -0400 X-Sasl-enc: 6h+QhbwaBWZxhhp+Zy5fGK/MTM1SvBnbAXB6UgzYp0FU 1188285335 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 6BB59B967; Tue, 28 Aug 2007 03:15:35 -0400 (EDT) Message-ID: <46D3CB96.5050109@FreeBSD.org> Date: Tue, 28 Aug 2007 08:15:34 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.4 (X11/20070630) MIME-Version: 1.0 To: Weiguang Shi References: <954767.6972.qm@web43139.mail.sp1.yahoo.com> In-Reply-To: <954767.6972.qm@web43139.mail.sp1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: nc captures 1024 bytes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2007 07:15:36 -0000 Looks like a netcat bug, if it doesn't tune buffers to the interface MTU. I'm not sure if nc has a 'de facto' maintainer however I believe it is something which was recently imported into the freebsd base system. Still, it is better to try to field patches with the upstream maintainer before filing a FreeBSD PR with your patches. regards, BMS