From owner-freebsd-questions@FreeBSD.ORG Fri Jun 24 13:24:11 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BE1016A41C for ; Fri, 24 Jun 2005 13:24:11 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out6.blueyonder.co.uk (smtp-out6.blueyonder.co.uk [195.188.213.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0B1943D1F for ; Fri, 24 Jun 2005 13:24:09 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out6.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Fri, 24 Jun 2005 14:24:50 +0100 Message-ID: <42BC0978.2020609@dial.pipex.com> Date: Fri, 24 Jun 2005 14:24:08 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: Joe References: <20050623182407.976.qmail@web41005.mail.yahoo.com> In-Reply-To: <20050623182407.976.qmail@web41005.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Jun 2005 13:24:50.0474 (UTC) FILETIME=[196090A0:01C578C0] Cc: freebsd-questions@freebsd.org Subject: Re: SMP and networking under FreeBSD 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2005 13:24:11 -0000 Joe wrote: >Okay, I've been looking and looking for duplicate natd's. > >I have the /etc/rc.conf which has natd stuff below, and the only >other place I see it is in ipfw. > >I was able to change my rc and use /etc/rc.d/natd start and that >works. Which is better as it does not require me to reload my >firewall rules. > >I still don't know why natd refuses to start the first time when >called from ipfw. > > If I understand the boot procedure correctly, natd ought to be started as part of the /etc/rc.d/ipfw and that just calls "/etc/rc.d/natd start" which is what you are typing later from the command line with success, so why it fails at boot, I really don't know at this point. The "cannot bind to divert socket" error I thought could happen if a) you weren't root (seems unlikely from bootup) or b) something had already bound the socket. After your machine boots, what does ps uagxww | egrep natd show? Google also found this: >- In FreeBSD, IPDIVERT must be enabled at compile time. > I guess your kernel has this option, or natd would never have worked. what ifconfig lines do you have in /etc.rc.conf egrep ifconfig /etc/rc.conf >I have no rc.conf.local > > Not too surprising. It could be used under 4.X as a second level to rc.conf, but exists nowadays for backwards compatibility and AFAIK isn't created by anything. As a more drastic attempt at a solution, could you try upgrading to 5.4? It has numerous improvements over 5.3, which was never a production release. Maybe some ordering problems was fixed. --Alex