Date: Mon, 4 Dec 2000 14:41:30 -0800 (PST) From: Gordon Tetlow <gordont@bluemtn.net> To: Charles Anderson <caa@columbus.rr.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: natd bug Message-ID: <Pine.BSF.4.05.10012041438210.19939-100000@sdmail0.sd.bmarts.com> In-Reply-To: <20001204135853.A24637@midgard.dhs.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It didn't seem to help for me. I still get lots of permission denied, but
then again, I'm also using a much stricter set of rules.
I seriously hope that the fact we are using 3com etherlink iii cards
doesn't have anything to do with it.
Just to note. As far as I can tell, it's still doing nat just fine, it's
just filling up my log.
-gordon
On Mon, 4 Dec 2000, Charles Anderson wrote:
> I had the same thing until I removed rule 200 in rc.firewall (using open)
> #${fwcmd} add 200 deny all from any to 127.0.0.0/8
>
> Now it works, but I feel a bit less secure, but I don't have anything of
> great importance on the box.
>
> One thing I noticed in common, is we're both running Etherlink III's.
> (although mine is isa and yours is PCI) I have a friend that a pair of fxp's,
> and I tried his rc.firewall, that works fine for him, but doesn't for me.
>
> -Charlie
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10012041438210.19939-100000>