Re: Linux 4.3.1 regression: -m state returns "Protocol wrong type for socket"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sunday 2015-12-13 01:05, Dâniel Fraga wrote:
>> git log --oneline v4.3..v4.3.1 net/netfilter/ | wc -l
>> 0
>> 
>> Now, that makes me wonder if 4.3.1 is the culprit, or whether your
>> surrounding system is. Like [...]
>
>	Anyway, don't you think nf_conntrack_ipv4 should be
>auto-selected when "state" module is selected?

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.
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux