Date: Fri, 24 Jun 2005 09:16:51 -0700 (PDT) From: Joe <josepha48@yahoo.com> To: Alex Zbyslaw <xfb52@dial.pipex.com> Cc: freebsd-questions@freebsd.org Subject: Re: SMP and networking under FreeBSD 5.3 Message-ID: <20050624161652.28509.qmail@web41015.mail.yahoo.com> In-Reply-To: <42BC0978.2020609@dial.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, ps: root 542 0.0 0.7 1320 812 ?? Ss Tue09AM 2:22.10 /sbin/natd -dynamic -d -log_ipfw_denied -log_denied -dynamic -n dc0 ifconfig: pccard_ifconfig="NO" ifconfig_xl0="inet 192.168.0.15 netmask 255.255.255.0" ifconfig_dc0="DHCP" So FreeBSD 5.3 isn't production? I had read somewhere that 5.2.1 wasn't production and that 5.3 was supposed to be production. I'll look into upgrading to 5.4, it will take a bit of time to do that though. Joe --- Alex Zbyslaw <xfb52@dial.pipex.com> wrote: > 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 > > ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050624161652.28509.qmail>