From owner-freebsd-questions@FreeBSD.ORG Tue Aug 30 12:31:25 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 909DA16A41F for ; Tue, 30 Aug 2005 12:31:25 +0000 (GMT) (envelope-from tinguely@casselton.net) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3086343D45 for ; Tue, 30 Aug 2005 12:31:25 +0000 (GMT) (envelope-from tinguely@casselton.net) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.12.11/8.12.11) with ESMTP id j7UCVNjG099929; Tue, 30 Aug 2005 07:31:23 -0500 (CDT) (envelope-from tinguely@casselton.net) Received: (from tinguely@localhost) by casselton.net (8.12.11/8.12.11/Submit) id j7UCVM3w099928; Tue, 30 Aug 2005 07:31:22 -0500 (CDT) (envelope-from tinguely) Date: Tue, 30 Aug 2005 07:31:22 -0500 (CDT) From: Mark Tinguely Message-Id: <200508301231.j7UCVM3w099928@casselton.net> To: hwh@gddsn.org.cn, questions@freebsd.org In-Reply-To: <431327BD.6030006@gddsn.org.cn> X-Spam-Status: No, score=1.4 required=5.0 tests=REPLY_TO_EMPTY autolearn=no version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on ccn.casselton.net Cc: Subject: Re: Question about TCP packet. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 12:31:25 -0000 > found that I received 2 ack packets when sent data to embedded device. > Does It mean one ack packet is not necessary and > the embedded device's tcp stack is broken? > > thanks, > --hwh > > > 16:58:08.448730 192.168.168.137.1693 > 211.96.21.220.9742: P 1:22(21) ack 1 win 65535 (DF) > 16:58:08.450458 211.96.21.220.9742 > 192.168.168.137.1693: . ack 22 win 1439 (DF) > 16:58:08.482349 211.96.21.220.9742 > 192.168.168.137.1693: . ack 22 win 1460 (DF) The second ack is a window update. The recieving TCP stack is telling the sender that the data has been consumed and more space is available for incoming data. If you increase your recieve buffer size on the "211.96.21.220" host, you will not see these updates for interactive data. --Mark Tinguely