Date: Fri, 21 Sep 2007 21:03:41 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: Petr Holub <hopet@ics.muni.cz> Cc: current@freebsd.org Subject: Re: TCP socket problem on Sept. -CURRENT snapshot Message-ID: <46F4158D.6030208@FreeBSD.org> In-Reply-To: <002c01c7fc45$717e6400$5317fb93@KLOBOUCEK> References: <002c01c7fc45$717e6400$5317fb93@KLOBOUCEK>
next in thread | previous in thread | raw e-mail | index | archive | help
Petr Holub wrote: > Hi, > > I've encountered the following problem while building xorg from > ports: > > TCP: [134.76.12.3]:21 to [147.251.54.186]:56914 tcpflags 0x18<PUSH,ACK>; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:62424 tcpflags 0x18<PUSH,ACK>; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:55989 tcpflags 0x18<PUSH,ACK>; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:52923 tcpflags 0x18<PUSH,ACK>; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > > It occurred from several different addresses and results in being > unable event to ping that IP until reboot. These log messages are informational, if you see ICMP problems it must have another source. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46F4158D.6030208>