From owner-freebsd-stable Sun Apr 30 0:17:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nerv.nu (cx639627-c.irvn1.occa.home.com [24.0.209.134]) by hub.freebsd.org (Postfix) with ESMTP id 805DE37B88A for ; Sun, 30 Apr 2000 00:17:46 -0700 (PDT) (envelope-from nugundam@nerv.nu) Received: from localhost (nugundam@localhost) by mail.nerv.nu (8.9.3/8.9.3) with ESMTP id AAA03195; Sun, 30 Apr 2000 00:17:51 -0700 (PDT) (envelope-from nugundam@greenwood3.nerv.nu) Date: Sun, 30 Apr 2000 00:17:51 -0700 (PDT) From: Joseph Lee To: freebsd-stable@freebsd.org Cc: luigi@info.iet.unipi.it Subject: ip_fw.c: /kernel: invalid state: 0x3 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After moving my 3.4S box to 4.0S today, I've been getting a lot of "/kernel: invalid state: 0x3" messages. Grepping through my mail spool, and /usr/src, it seems it's related to ip_fw.c where it checks for a invalid state in the statefullness of the firewall rules. Going by the previous emails which went over this, I don't have any keep-state rules on ip, just tcp rules, and udp rules. The error code is 0x3 which looks like a TH_SYN | TH_FIN. I do have SYNFIN drop sysctl compiled in the kernel, but it's not enabled. Is this some strange interaction here? -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 2000 >> www.anime-expo.org/ > # FreeBSD: The Power to Serve >> www.freebsd.org > # The Ultimate Online Speed-Shop >> www.racesearch.com / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message