Date: Sun, 28 Feb 1999 09:48:06 -0600 From: Guy Helmer <ghelmer@scl.ameslab.gov> To: + + <uvatha@my-dejanews.com> Cc: freebsd-questions@freebsd.org Subject: Re: natd locks up? Message-ID: <Pine.SGI.4.05.9902280946090.25226-100000@demios.scl.ameslab.gov> In-Reply-To: <GFHJGKCBAGIPAAAA@my-dejanews.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 28 Feb 1999, + + wrote: > After spending several hours browsing mailing list archives about natd > problems, I've determined that my problem seems to be unique. Simply > put, natd doesn't even get far enough to start listening on its > assigned port (8668 in my stock 2.2.7 setup, as defined in > /etc/services). After executing natd (usually in the form of natd -u > -n fxp0, although I've also through -p 8668 in there for kicks), > netstat -a doesn't show natd or port 8668 anywhere! (the output is > indentical to the output prior to running natd, as confirmed by diff). > Stranger still, natd seems to be locked up pretty hard - the only way > to get rid of it is kill -9 (regular kill has no effect). > /var/log/alias.log is always empty, and using -v for natd never prints > any text to the console whatsoever. Have you rebuilt your kernel with IPFIREWALL and IPDIVERT options? Guy Helmer, Ph.D. Candidate, Iowa State University Dept. of Computer Science Research Assistant, Ames Laboratory --- ghelmer@scl.ameslab.gov Research Assistant, Dept. of Computer Science --- ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SGI.4.05.9902280946090.25226-100000>