From owner-freebsd-bugs Tue Sep 25 10:33: 2 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 4C34137B414 for ; Tue, 25 Sep 2001 10:30:10 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f8PHTX858215; Tue, 25 Sep 2001 20:29:33 +0300 (EEST) (envelope-from ru) Date: Tue, 25 Sep 2001 20:29:33 +0300 From: Ruslan Ermilov To: Poul-Henning Kamp Cc: fj@batmule.dk, freebsd-bugs@FreeBSD.ORG Subject: Re: misc/30255: [PATCH] Packets reinjected by natd but denied by ipfw generates annoying errors Message-ID: <20010925202933.A57333@sunbay.com> References: <200109251427.f8PERJL37187@freefall.freebsd.org> <31664.1001438088@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <31664.1001438088@critter>; from phk@critter.freebsd.dk on Tue, Sep 25, 2001 at 07:14:48PM +0200 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Sep 25, 2001 at 07:14:48PM +0200, Poul-Henning Kamp wrote: > > >State-Changed-From-To: open->closed > >State-Changed-By: ru > >State-Changed-When: Tue Sep 25 07:24:17 PDT 2001 > >State-Changed-Why: > > >With my MAINTAINER hat on, I don't like this option. > > > >This error usually indicates a misconfigured firewall. > >It is almost always possible to write firewall rules > >that do not result in EACCES from firewall. > > I think you're being too harsh here Ruslan. While it may theoretically > be possible to write such rules, I have myself often found it simpler > and faster to reject on the "backside" of natd. > Just give me one real example where it's really useful, and I'll probably agree. > Considering what is proposed is an option I think it should be committed. > OK, how about this instead? I can change the code so that it logs various warnings at different syslog(3) levels. Then what gets logged may be controlled via syslog.conf(5). Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message