Date: Sun, 03 Jul 2005 00:04:49 -0500 From: Billy Newsom <smartweb@leadhill.net> To: Hans Lambermont <hans@lambermont.dyndns.org>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: rcorder for FreeBSD 5.3? Message-ID: <42C771F1.5020509@leadhill.net> In-Reply-To: <20050702204257.GA2844@leia.lambermont.dyndns.org> References: <42C6F7E1.4060704@leadhill.net> <20050702204257.GA2844@leia.lambermont.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hans Lambermont wrote: > Billy Newsom wrote: > > >>Does anyone have FreeBSD 5.3 installed (preferably a version compiled >>before March 2005) > > > FreeBSD 5.3-RELEASE #3: Sun Dec 19 14:54:18 CET 2004 > > >>What is the output for this command under FreeBSD 5.3? >>sh -c "cd /etc/rc.d ; rcorder -s nostart * 2>/dev/null" > > > preseedrandom > initdiskless > rcconf.sh > initrandom > dumpon > vinum > gbde_swap > gbde > ccd > swap1 > early.sh > fsck > root > mountcritlocal > ipfilter > var > cleanvar > addswap > sysctl > hostname > ipmon > random > adjkerntz > atm1 > ipnat > ipfs > kldxref > sppp > serial > pccard > netif > isdnd > ppp-user > ipfw > dhclient > nsswitch > ip6addrctl > atm2 > routing > ip6fw > network_ipv6 > mroute6d > route6d > mrouted > routed > NETWORKING > devd > mountcritremote > lomac > syslogd > savecore > SERVERS > named > ntpdate > rpcbind > nisdomain > ypxfrd > ypserv > ypupdated > ypbind > ypset > yppasswdd > accounting > nfsclient > amd > atm3 > tmp > cleartmp > dmesg > ike > ipsec > ipxrouted > kerberos > kadmind > keyserv > kpasswdd > ldconfig > quota > nfsserver > mountd > nfsd > nfslocking > pflog > pf > pppoed > pwcheck > virecover > DAEMON > watchdogd > usbd > ugidfw > timed > apm > apmd > bootparams > local > lpd > motd > ntpd > rarpd > rtadvd > rwho > LOGIN > syscons > sshd > sendmail > archdep > abi > cron > devfs > jail > localpkg > netoptions > securelevel > resolv > pcvt > othermta > msgs > moused > mixer > inetd > bgfsck > > -- Hans Hmm. That's interesting. Thanks. Here's a diff I ran on the two outputs. Notice that the ipfilter script is in a different spot, but just barely. Although I was trying to make something of the situation, I don't immediately see how it can make a big difference. I was really trying to see if/how ipnat would stop working (at least immediately after reboot) until I flushed and reloaded ipnat. #diff -u 53.txt 54.txt --- 53.txt Sat Jul 2 23:05:19 2005 +++ 54.txt Sat Jul 2 23:06:17 2005 @@ -12,9 +12,9 @@ fsck root mountcritlocal -ipfilter var cleanvar +ipfilter addswap sysctl hostname @@ -95,6 +95,7 @@ bootparams local lpd +mixer motd ntpd rarpd @@ -117,6 +118,5 @@ othermta msgs moused -mixer inetd bgfsck Anyhow, I don't see what bearing any of this would have on ipnat mysteriously stop working for me. The only thing I see is that I might have at some point started using interface renaming. The only thing I can figure at this point by looking into this is that when I edited ipnat.rules, I used my renamed interfaces, just as I did in ipf.rules. What I see in the rcorder outputs is that /etc/rc.d/netif comes after /etc/rc.d/ipnat. In other words, perhaps my interface names in my ipnat.rules file is being loaded during bootup *before* those interface names exist! If so, ipnat would act weirdly, perhaps. One of the routines run by /etc/rc.d/netif on line 69 is /etc/rc.d/ipfilter resync which seems to resync ipfilter, but not ipnat. What I see is that it seems like renaming interfaces *might* have broken ipnat. And that might explain why I have to manually run "/sbin/ipnat -CF -f /etc/ipnat.rules" after every boot. I think I will script this, and watch the output of ipnat -l. As far as I know, ipnat was supposed to work fine with renamed interfaces, but maybe not.... dunno. Billy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42C771F1.5020509>