From owner-freebsd-questions Sat Nov 25 17:15:27 2000 Delivered-To: freebsd-questions@freebsd.org Received: from rmx194-mta.mail.com (rmx194-mta.mail.com [165.251.48.41]) by hub.freebsd.org (Postfix) with ESMTP id D0AC537B4C5 for ; Sat, 25 Nov 2000 17:15:25 -0800 (PST) Received: from weba3.iname.net (weba3.iname.net [165.251.4.13]) by rmx194-mta.mail.com (8.9.3/8.9.3) with ESMTP id UAA23812; Sat, 25 Nov 2000 20:15:21 -0500 (EST) From: thursday@altavista.net Received: (from root@localhost) by weba3.iname.net (8.9.1a/8.9.2.Alpha2) id UAA22882; Sat, 25 Nov 2000 20:07:47 -0500 (EST) MIME-Version: 1.0 Message-Id: <0011252007473V.12620@weba3.iname.net> Date: Sat, 25 Nov 2000 20:07:47 -0500 (EST) Content-Type: Text/Plain Content-Transfer-Encoding: 7bit To: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I installed FreeBSD 4.2-RELEASE yesterday on my Pentium-II 266 machine, and I'm having a couple of issues... 1) Twice now, wtmp has become corrupted (ac -p reports root's total login time as -378999.4). last reports a bunch of normal logins except for one or two in the middle happening in December. My question: What is the cause of this? Is there a better way to fix it (or edit wtmp) other than cat > /var/log/wtmp ^d? The machine is connected to a timeserver, and date has never reported anything but the correct date. 2) The machine is going to act as a gateway/router for my internal network. I've compiled a new kernel, setup rc.conf, setup my firewall (I used rc.conf and rc.firewall from the machine that this new machine is replacing (a freebsd 3.4 system), adjusting where necessary for the different ethernet device names), and all mostly works well (My isp's nameservers went down during the middle of this process, making setup & troubleshooting really lots of fun) except: the console & system log frequently report: "Nov 25 13:44:47 saucer natd[147]: failed to write packet back (Permission denied) Nov 25 13:44:53 saucer last message repeated 4 times " My questions are: What's up with this? Is this due to my firewall rules, or something else? I have log no set in /etc/natd.conf, and I'd rather not see this message if it's not affecting performance. I never saw this before on my 3.4 system. If there are some relevant files I can attach to help troubleshooting, please let me know. Thanks for any insight any of you can give me... ---------------------------------------------------------------- Get your free email from AltaVista at http://altavista.iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message