On Sunday 2015-12-13 01:32, Dâniel Fraga wrote: >On Sun, 13 Dec 2015 01:30:17 +0100 (CET) >Jan Engelhardt <jengelh@xxxxxxx> wrote: > >> nf_conntrack_ipv4 is indeed autoloaded (provided modprobe can do it) >> when you cause instantiation of a xt_conntrack (or xt_state) rule >> object through ip(4)tables. And if modprobe cannot satisfy the >> request, that feeds back through the kernel and to iptables, which >> may then report it to stderr. > > No, I mean selected in the "make menuconfig" ;) If the user >chooses to compile state module, menuconfig won't select automatically >nf_conntrack_ipv4 (and it should, since it depends on it). There is nothing to add to Kconfig, because there is no build-time dependency here. In addition, some people might get grumpy if the CONFIG_NETFILTER_XT_MATCH_CONNTRACK gained a dependency on something it does not depend on at runtime in 100% of cases. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
