Fernando de Oliveira wrote: >> The way to correct it would be to set CONFIG_IP_NF_TARGET_LOG=y in the >> kernel configuration. You may be looking in the wrong place. There >> are a lot of netfilter options. > > There is no such option anymore. > > I have the following related options set: > # grep CONFIG /boot/config-3.4.0 | grep -i ip | grep -i target | grep -i log > CONFIG_IP_NF_TARGET_ULOG=y
Well I get: $ grep _NF_ config-3.3.6-20120515 |grep LOG CONFIG_IP_NF_TARGET_LOG=y CONFIG_IP_NF_TARGET_ULOG=y CONFIG_IP6_NF_TARGET_LOG=y Maybe it changed in the 3.4 kernel. > Here, I end the inline reply. > > Now, the solution. I decided to "make -j4" with the "oldconfig" from > 3.3.6 again, instead of trying to start with the one from 3.4.0. Lots of > questions, suddenly > > LOG target support (NETFILTER_XT_TARGET_LOG) [N/m/y/?] (NEW) y > > thus, previously I did differently and did not notice this. With just > this, and commenting out modprobe ipt_LOG (as written above), *problem > solved*!!! I decided for this option, after you both mentioned the *LOG > options. Good detective work. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
