From owner-freebsd-security Thu Jan 25 21:56:46 2001 Delivered-To: freebsd-security@freebsd.org Received: from athena.za.net (athena.za.net [196.30.167.200]) by hub.freebsd.org (Postfix) with ESMTP id B945937B400; Thu, 25 Jan 2001 21:56:23 -0800 (PST) Received: from localhost (jus@localhost) by athena.za.net (8.9.3/8.9.3) with ESMTP id GAA00412; Fri, 26 Jan 2001 06:00:24 GMT (envelope-from jus@security.za.net) X-Authentication-Warning: athena.za.net: jus owned process doing -bs Date: Fri, 26 Jan 2001 08:00:04 +0200 (SAST) From: Justin Stanford X-Sender: jus@athena.za.net To: questions@freebsd.org Cc: security@freebsd.org Subject: ipfw security patch problem.. 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 Hi, I upgraded my ipfw yesterday on my 4.0-STABLE system with the patch by following the instructions to the letter for the security bug discovered by Aragon Gouveia, and compile and install appeared to go seamlessly. However, ipfw now gives me this type of problem: [root@athena]~# ipfw add 5000 deny tcp from any to 196.30.167.200 515 via rl0 05000 deny tcp from any to 196.30.167.200 515 via rl0 ip_fw_ctl: empty interface name ipfw: setsockopt(IP_FW_ADD): Invalid argument [root@athena]~# The interface is most definitely rl0, and this exact ruleset is the same I have been using for ages with my previous ipfw. Suggestions? -- Justin Stanford 082 7402741 jus@security.za.net www.security.za.net IT Security and Solutions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message