Date: Sun, 31 Aug 2008 11:06:18 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: ben wilber <ben@desync.com> Cc: freebsd-pf@freebsd.org Subject: Re: pf and mxge Message-ID: <20080831180618.GA34269@icarus.home.lan> In-Reply-To: <20080831172943.GA26180@exodus.desync.com> References: <20080829105422.GI1644@exodus.desync.com> <20080829110358.GA72503@icarus.home.lan> <20080829125549.GR64444@egr.msu.edu> <20080831172943.GA26180@exodus.desync.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 31, 2008 at 01:29:43PM -0400, ben wilber wrote: > 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? A new NIC wouldn't have had anything to do with the problem; it's probably always been there, or you just didn't notice it before. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080831180618.GA34269>