From owner-freebsd-stable Thu Mar 14 8:47:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from bast.unixathome.org (bast.unixathome.org [216.187.105.150]) by hub.freebsd.org (Postfix) with ESMTP id 1BA6637B402 for ; Thu, 14 Mar 2002 08:47:24 -0800 (PST) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 4E1543F0E for ; Thu, 14 Mar 2002 11:47:23 -0500 (EST) From: "Dan Langille" Organization: DVL Software Limited To: freebsd-stable@FreeBSD.ORG Date: Thu, 14 Mar 2002 11:47:21 -0500 MIME-Version: 1.0 Subject: ipfilter keep state broken? Reply-To: dan@langille.org X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Message-Id: <20020314164723.4E1543F0E@bast.unixathome.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I upgraded my webserver on March 9 from the post 4.5-RELASE stable. Today I've been noticing very unusal access issues on the box. For example, I could not get to my webserver from one remote box using https. I had to change my rules before it would work: Here is the after and before. I had to replace the keep state with two rules (a.c.b.d is the IP address in question): < pass in quick proto tcp from a.b.c.d/32 to any port = https < pass out quick proto tcp from any to a.b.c.d/32 port = https --- > pass in quick proto tcp from a.b.c.d/32 to any port = https flags S keep state Anyone else seeing similar problems? FWIW, the problem started at about 1:01AM EST today. It's a stretch to associate a keep state problem which appears 5 days after an upgrade with a possible -STABLE issue. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message