Date: Sun, 28 Feb 1999 11:13:33 -0000 From: "+ +" <uvatha@my-dejanews.com> To: freebsd-questions@freebsd.org Subject: natd locks up? Message-ID: <GFHJGKCBAGIPAAAA@my-dejanews.com>
next in thread | raw e-mail | index | archive | help
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. In short, it seems that natd seems to be locking up hard, early in the program. What could cause this? -----== Sent via Deja News, The Discussion Network ==----- http://www.dejanews.com/ Easy access to 50,000+ discussion forums 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?GFHJGKCBAGIPAAAA>