From owner-freebsd-pf@FreeBSD.ORG Sun Aug 31 17:30:05 2008 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4749106566B for ; Sun, 31 Aug 2008 17:30:05 +0000 (UTC) (envelope-from bw@exodus.desync.com) Received: from exodus.desync.com (desync.com [IPv6:2607:f178::165]) by mx1.freebsd.org (Postfix) with ESMTP id 7D7438FC0A for ; Sun, 31 Aug 2008 17:30:05 +0000 (UTC) (envelope-from bw@exodus.desync.com) Received: from exodus.desync.com (localhost [127.0.0.1]) by exodus.desync.com (8.14.2/8.14.2) with ESMTP id m7VHTiuF026220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 Aug 2008 13:29:44 -0400 (EDT) (envelope-from bw@exodus.desync.com) Received: (from bw@localhost) by exodus.desync.com (8.14.3/8.14.2/Submit) id m7VHThYO026219; Sun, 31 Aug 2008 13:29:43 -0400 (EDT) (envelope-from bw) Date: Sun, 31 Aug 2008 13:29:43 -0400 From: ben wilber To: Adam McDougall Message-ID: <20080831172943.GA26180@exodus.desync.com> References: <20080829105422.GI1644@exodus.desync.com> <20080829110358.GA72503@icarus.home.lan> <20080829125549.GR64444@egr.msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080829125549.GR64444@egr.msu.edu> X-Angst-Level: High User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-pf@freebsd.org Subject: Re: pf and mxge X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2008 17:30:06 -0000 On Fri, Aug 29, 2008 at 08:55:49AM -0400, Adam McDougall wrote: > I've seen this problem on RELENG_6, although the SSH connections > would not "time out" -- after a page or so of 'dmesg' output, they > would immediately get disconnected/severed. I believe the problem was > caused by my use of "modulate state" instead of "keep state" (since on > RELENG_6 "keep state" is not implicit). Bingo. The problem was "modulate state". Sorry if the answer is obvious, but any idea why a new NIC might have aggravated this? In any case, thanks! bw.