rcorder for FreeBSD 5.3?
smartweb at leadhill.net
Sun Jul 3 06:05:49 GMT 2005
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"
> -- 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 @@
@@ -95,6 +95,7 @@
@@ -117,6 +118,5 @@
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
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.
More information about the freebsd-stable