I used to get this exact same message, although my natd setup worked just
fine. It was just filling up the logs. I then added -log_denied to the
arguements for natd and it stopped spewing log messages. Here's what I
run:
/sbin/natd -unregistered_only -use_sockets -punch_fw 5050:10 -log_denied -n vx0
I don't know if this helps out your problem or not, but at least I don't
get really annoying syslog messages every minute.
-gordon
On Thu, 30 Nov 2000, Frederik Meerwaldt wrote:
> I was just looking why my natd doesnt work, when I discovered the
> following bug (?):
>
> I compiled my kernel with IPDIVERT IPFIREWALL and
> IPFIREWALL_DEFAULT_TO_ACCEPT and I set up only one rule:
> ipfw add divert natd all from any to any via isp0
> Then I started natd (at boot time):
> natd -unregistered_only -dynamic -n isp0
> But when a package arrives (doesn't matter from localhost or another
> host), natd gives out a kernel message:
>
> Nov 30 15:03:06 server natd[195]: failed to write packet back (Permission
> denied)
>
> What does that mean? I started natd from my rc.local, so it runs as root
> and it should have all permissions.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
