From owner-freebsd-current@FreeBSD.ORG Sun Jul 1 08:58:24 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D922016A41F for ; Sun, 1 Jul 2007 08:58:24 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id A3F3413C447 for ; Sun, 1 Jul 2007 08:58:24 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at inter-sonic.com Message-ID: <46876CAB.1050204@intersonic.se> Date: Sun, 01 Jul 2007 10:58:19 +0200 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 2.0.0.0 (X11/20070422) MIME-Version: 1.0 To: Rong-en Fan References: <6eb82e0706302221p3c4e24edo2f62e6ba60958b4f@mail.gmail.com> <6eb82e0707010013l7e7ce403h80942325a2b5ca73@mail.gmail.com> In-Reply-To: <6eb82e0707010013l7e7ce403h80942325a2b5ca73@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: tcp_input: Listen socket: Spurious RST, segment rejected 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: Sun, 01 Jul 2007 08:58:24 -0000 Rong-en Fan wrote: > On 7/1/07, Rong-en Fan wrote: >> Hi, >> >> I'm runnnig rsyncd on an i386 with Jun 19 -current. >> Once I lanuch rsync client from another host running >> 6.2-STABLE, I saw lots of >> >> TCP: [192.168.30.48]:64597 to [192.168.30.69]:873 tcpflags 0x4; >> tcp_input: Listen socket: Spurious RST, segment rejected >> TCP: [192.168.30.48]:64597 to [192.168.30.69]:873 tcpflags 0x4; >> tcp_input: Listen socket: Spurious RST, segment rejected >> >> and the rsync client stops with various error messages. >> It's really annoying. Any ideas? > > Turn off IPSEC seems help my situation. Hi, I see same thing and just out of curiosity, where did you turn off IPSEC? Thanks, /po