Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Mar 2002 12:30:38 -0500
From:      Chris Johnson <cjohnson@palomine.net>
To:        Dan Langille <dan@langille.org>
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: ipfilter keep state broken?
Message-ID:  <20020314123038.B43330@palomine.net>
In-Reply-To: <20020314172627.DEF953F0E@bast.unixathome.org>; from dan@langille.org on Thu, Mar 14, 2002 at 12:26:27PM -0500
References:  <20020314164723.4E1543F0E@bast.unixathome.org>; <20020314121048.A43100@palomine.net> <20020314172627.DEF953F0E@bast.unixathome.org>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Thu, Mar 14, 2002 at 12:26:27PM -0500, Dan Langille wrote:
> On 14 Mar 2002 at 12:10, Chris Johnson wrote:
> 
> > On Thu, Mar 14, 2002 at 11:47:21AM -0500, Dan Langille wrote:
> > > 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
> > 
> > Could it be that this didn't actually fix your problem but that you made some
> > other change in the process? For example, did you flush your state table? Is it
> > possible that it was getting full?
> 
> I agree with your theory.  Thank you.
> 
> After doing an ipf -FS to clear the state table, everything was still 
> working fine.  Then I reinstated my keep state rules and things went back 
> to normal.
> 
> Any suggestions to avoid this problem in future?  Thanks.

Do all of the "pass...proto tcp...keep state" lines in your rules file include
"flags S"? I recently had a similar problem caused by my leaving out flags S on
a tcp keep state rule.

Chris

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE8kN49yeUEMvtGLWERAhv7AKDvPAjJEqXpnw+ASnEH0lyR0HNLBgCgwBjo
FrpWcrSy/sDJIhmKyv+ikgs=
=69El
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020314123038.B43330>