From owner-freebsd-security Thu Oct 29 00:02:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17256 for freebsd-security-outgoing; Thu, 29 Oct 1998 00:02:32 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17251 for ; Thu, 29 Oct 1998 00:02:30 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id DAA14965 for ; Thu, 29 Oct 1998 03:02:28 -0500 (EST) Date: Thu, 29 Oct 1998 03:02:31 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-security@FreeBSD.ORG Subject: IPFW problems... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Im at a loss for this problem I am having with IPFW in 2.2.7-stable. I have a kernel that I built with 2.2.7-RELEASE before cvsuping kernel source to stable. It has firewall support in it and boots fine with a firewall type of open. But EVERY kernel I build from stable wedges the machine, with the following errors: Oct 28 15:56:54 pm330 /kernel: FreeBSD 2.2.7-STABLE #0: Wed Oct 28 15:54:08 CST 1998 Oct 28 15:56:54 pm330 /kernel: ed0 at 0x280-0x29f irq 10 on isa Oct 28 15:56:54 pm330 /kernel: ed0: address 00:80:ad:b3:16:15, type NE2000 (16 bit) Oct 28 15:56:55 pm330 /kernel: 1 3C5x9 board(s) on ISA found at 0x300 Oct 28 15:56:55 pm330 /kernel: ep0 at 0x300-0x30f irq 5 on isa Oct 28 15:56:55 pm330 /kernel: ep0: utp[*UTP*] address 00:10:5 Oct 28 15:56:55 pm330 /kernel: a:1c:8c:ee Oct 28 15:56:55 pm330 /kernel: IP packet filtering initialized, divert enabled, logging disabled Oct 28 15:56:56 pm330 xntpd[107]: using xntpd phase-lock loop Oct 28 15:56:57 pm330 xntpd[107]: sendto(128.252.19.1): Permission denied Oct 28 15:56:58 pm330 xntpd[107]: sendto(128.105.201.11): Permission denied Oct 28 15:59:54 pm330 syslogd: exiting on signal 15 And on numerous occasions I have received this which I have never seen. Oct 28 15:56:55 pm330 /kernel: ip_fw_ctl: len=104, want 96 Right after the IP packet filtering initialized, etc.. message is when this shows up. I searched the arvhices for the error I get at console: ipfw: setsockopt(IP_FW_ADD): Invalid argument And I *DO* have IPFIREWALL and IPDIVERT in the kernel config. No matter how many times I rebuild the 2.2.7-STABLE kernel it will not boot but throws out the above errors, booting the old 2.2.7-RELEASE kernel works fine. And this puzzles me. Its an open type of firewall, and nothing changes configuration wise between booting the 2.2.7-RELEASE kernel and the 2.2.7-STABLE kernel. Something in the kernel is doing it. The rc.firewall is the same, the firewall type in rc.conf is the same. The only thing I see from the mail archives is not adding the IPFIREWALL and IPDIVERT options the kernel, and there both in there. Anyone have an idea? Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message