From owner-freebsd-current@FreeBSD.ORG Mon Aug 6 23:02:01 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 D346016A418 for ; Mon, 6 Aug 2007 23:02:01 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [80.68.94.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7F74913C459 for ; Mon, 6 Aug 2007 23:02:01 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: by muon.bluestop.org (Postfix, from userid 1000) id 95033404D; Mon, 6 Aug 2007 23:41:12 +0100 (BST) Date: Mon, 6 Aug 2007 23:41:12 +0100 From: bruce@cran.org.uk To: current@freebsd.org Message-ID: <20070806224112.GA21876@muon.bluestop.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: "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: Mon, 06 Aug 2007 23:02:01 -0000 I cvsupped my -CURRENT laptop last night and have been building ports today. When I checked the dmesg there were lots of messages similar to: TCP: [204.152.184.73]:21 to [10.0.10.13]:65159] tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received data after socket was closed, sending RST and removing tcpcb The machine's uname: FreeBSD muon.draftnet 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Sun Aug 5 23:58:47 BST 2007 brucec@muon.draftnet:/usr/obj/usr/src/sys/INSPIRON amd64 The laptop is connected to a machine running a month-old -CURRENT; it's running NAT via PF to my LAN using if_bridge. Apart from removing unused drivers, the laptop's kernel configuration has HZ set to 100 and I've added PF. -- Bruce Cran