Date: Tue, 14 Aug 2007 15:31:50 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Eygene Ryabinkin <rea-fbsd@codelabs.ru> Cc: current@freebsd.org, Stefan Lambrev <stefan.lambrev@moneybookers.com> Subject: Re: "tcpflags 0x18<PUSH,ACK>; tcp_do_segment" kernel messages Message-ID: <20070814193150.GA21553@rot26.obsecurity.org> In-Reply-To: <20070814145759.GB25169@void.codelabs.ru> References: <20070806224112.GA21876@muon.bluestop.org> <20070807073920.GV50228@void.codelabs.ru> <46C18B60.8050400@moneybookers.com> <20070814145759.GB25169@void.codelabs.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070814193150.GA21553>