From owner-freebsd-current@FreeBSD.ORG Tue Aug 14 19:31:51 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7752616A421 for ; Tue, 14 Aug 2007 19:31:51 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 69DB213C45E for ; Tue, 14 Aug 2007 19:31:51 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8C9831A4D7C; Tue, 14 Aug 2007 12:30:27 -0700 (PDT) Received: by rot26.obsecurity.org (Postfix, from userid 1001) id A542FC134; Tue, 14 Aug 2007 15:31:50 -0400 (EDT) Date: Tue, 14 Aug 2007 15:31:50 -0400 From: Kris Kennaway To: Eygene Ryabinkin Message-ID: <20070814193150.GA21553@rot26.obsecurity.org> References: <20070806224112.GA21876@muon.bluestop.org> <20070807073920.GV50228@void.codelabs.ru> <46C18B60.8050400@moneybookers.com> <20070814145759.GB25169@void.codelabs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070814145759.GB25169@void.codelabs.ru> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org, Stefan Lambrev Subject: Re: "tcpflags 0x18; tcp_do_segment" kernel messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 14 Aug 2007 19:31:51 -0000 On Tue, Aug 14, 2007 at 06:57:59PM +0400, Eygene Ryabinkin wrote: > Stefan, good day. > > Tue, Aug 14, 2007 at 02:00:48PM +0300, Stefan Lambrev wrote: > > >If you were running -CURRENT on the same machine prior to CVSupping, > > >then you probably saw the 'Spurious RST' messages. They were > > >provoked by the same situation. The messages themselves are harmless, > > > > > This is not harmless here :( > > Yep, sorry. What I meant is that 'I had no problems with them' ;)) > > > I'm running current from today 14.Aug. > > I use an network applications that hangs every time when I see such a message. > > > > Any ideas how can I debug, or help to someone who is familiar with the code ? > > You can provide the tcpdump's raw dump of the session (sniffed with > the -s 1500 or whatever MTU you have). This may sched some light. tcpdump will probably be essential. Kris