Date: Sat, 2 Dec 2000 00:22:22 +0100 From: Thomas Moestl <tmoestl@gmx.net> To: freebsd-hackers@freebsd.org Subject: Re: natd bug Message-ID: <20001202002222.A2616@crow.dom2ip.de> In-Reply-To: <Pine.BSF.4.21.0011302021590.20212-100000@server.wes.mee.com>; from frederik@freddym.org on Thu, Nov 30, 2000 at 08:25:15PM %2B0100 References: <Pine.BSF.4.21.0011302021590.20212-100000@server.wes.mee.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 30, 2000 at 08:25:15PM +0100, Frederik Meerwaldt wrote: > 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) Is your link up at that time? The usual setup for a sppp device using dynamic ip's is an invalid ip (0.0.0.0) that is changed once an ip was assigned. So, if you are not dialled in, the invalid ip will be put in by natd, and that usually causes this error message. - Thomas 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?20001202002222.A2616>