Date: Thu, 13 Nov 1997 13:30:24 -0200 (EDT) From: Joao Carlos Mendes Luis <jonny@coppe.ufrj.br> To: stable@FreeBSD.ORG Subject: Re: Firewall Race ? Message-ID: <199711131530.NAA29230@gaia.coppe.ufrj.br> In-Reply-To: <199711130407.CAA17788@gaia.coppe.ufrj.br> from Joao Carlos Mendes Luis at "Nov 13, 97 02:07:39 am"
next in thread | previous in thread | raw e-mail | index | archive | help
#define quoting(Joao Carlos Mendes Luis) // Sorry for sending a "bug report" without more info, but since I upgraded // from 2.1-stable to 2.2-stable, I cross my fingers everytime I have to // reload the ipfw code. There are big chances that the hole system will // crash, if not during the reload, sometime after very soon. // // Has anybody else seen this ? // // My ipfw config has around 85 rules, and is still under developement, // so I have to clean and reload it sometimes. I've already had some suggestions, but none has an explanation for the problem. Let me try to clarify it. For crashing I mean just freezing or even a panic. I may get more detail the next time it happens. It's not that I'm getting locked outside of my machine or that logs can't reach syslog. My firewall reload program does not use "ipfw flush", instead, it cleans rule by rule, leaving just the last one, which is "pass all from any to any", so I don't have any lockup problem. Looking at the behaviour, I just can think of a race condition in the ipfw setup code. A stack trace shows nothing useful, making me believe the panic occurs in interrupt context. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711131530.NAA29230>