From owner-freebsd-current@FreeBSD.ORG Sat Aug 30 09:19:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5949516A4C0; Sat, 30 Aug 2003 09:19:20 -0700 (PDT) Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc2.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 204AA43FFB; Sat, 30 Aug 2003 09:19:19 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: by mailhub.yumyumyum.org (Postfix, from userid 1001) id 4CDD567; Sat, 30 Aug 2003 12:19:02 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mailhub.yumyumyum.org (Postfix) with ESMTP id 4140018; Sat, 30 Aug 2003 12:19:02 -0400 (EDT) Date: Sat, 30 Aug 2003 12:19:02 -0400 (EDT) From: Kenneth Culver To: Robert Watson In-Reply-To: Message-ID: <20030830121630.F28935@alpha.yumyumyum.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: 2 ports broken after gcc import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Aug 2003 16:19:20 -0000 > I just built a fresh nmap on my -current box and it appears to work fine > for me, as did the older nmap. So I guess that leaves me firmly in the > "unable to reproduce" camp. I have noticed that, on my wi0 boxes, I > tend to get a fair number of ENOBUFS errors when nmaping, but that > appears to be unrelated to the presence of UFS_ACL in the kernel. > > Are your different boxes using the same type of network interface? Do > you rely on routed or use static routes? If you tcpdump the interface, > do any nmap packets get out -- for example, the initial ping it performs > before scanning a host, or none? Well, on one of my boxes, I have IPFILTER, but no ACL's and it works fine, on the one that was previously not working, I had IPFILTER (but with no rules set) and ACL's. I removed all references to ipfilter from rc.conf (my ipf.rules and ipnat.rules were blank), removed IPFILTER and ACL from the kernel, recompiled, and rebooted, and it started working. So now I just have to go back and figure out which knob I turned to fix things. I'm running late now though so I'll let you know as soon as I can get back to it (the computer that was really having the problems was at work, so I can't get to it until tuesday). Ken