From: "Dâniel Fraga" <fragabr@gmail.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: "Florian Westphal" <fw@strlen.de>,
"Noel Kuntze" <noel@familie-kuntze.de>,
"Jozsef Kadlecsik" <kadlec@blackhole.kfki.hu>,
"Remzi AKYÜZ" <linuxliste@gmail.com>,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: Linux 4.3.1 regression: -m state returns "Protocol wrong type for socket"
Date: Sat, 12 Dec 2015 22:05:17 -0200 [thread overview]
Message-ID: <566cb640.46dc0d0a.5c3cc.287a@mx.google.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1512130032300.32038@nerf40.vanv.qr>
On Sun, 13 Dec 2015 00:34:02 +0100 (CET)
Jan Engelhardt <jengelh@inai.de> 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, someone once inserted the module into
> the running system without adding it to /etc/modprobe.d, and now a
> recent reboot exposed the issue.
I don't think so. I maintain my own Linux setup (like Linux
from scratch). Everything was fine until 4.3.1. Nothing else was
changed.
Anyway, don't you think nf_conntrack_ipv4 should be
auto-selected when "state" module is selected?
--
Linux 4.3.2: Blurry Fish Butt
http://www.youtube.com/DanielFragaBR
http://exchangewar.info
Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL
next prev parent reply other threads:[~2015-12-13 0:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <n4g4s8$4pr$1@ger.gmane.org>
[not found] ` <566BEF33.7090501@gmail.com>
2015-12-12 10:18 ` Linux 4.3.1 regression: -m state returns "Protocol wrong type for socket" Jozsef Kadlecsik
2015-12-12 11:50 ` Remzi AKYÜZ
2015-12-12 12:04 ` Jozsef Kadlecsik
2015-12-12 12:09 ` Noel Kuntze
2015-12-12 16:06 ` Dâniel Fraga
2015-12-12 19:32 ` Pablo Neira Ayuso
2015-12-12 19:35 ` Dâniel Fraga
2015-12-12 19:42 ` Dâniel Fraga
2015-12-12 23:20 ` Florian Westphal
2015-12-12 23:31 ` Dâniel Fraga
2015-12-12 23:34 ` Jan Engelhardt
2015-12-13 0:05 ` Dâniel Fraga [this message]
2015-12-13 0:30 ` Jan Engelhardt
2015-12-13 0:32 ` Dâniel Fraga
2015-12-13 0:47 ` Jan Engelhardt
2015-12-14 20:47 ` Jozsef Kadlecsik
2015-12-14 20:55 ` Pablo Neira Ayuso
2015-12-14 21:19 ` Jozsef Kadlecsik
2015-12-14 21:21 ` Jozsef Kadlecsik
2015-12-12 19:10 ` Pablo Neira Ayuso
2015-12-12 19:22 ` Noel Kuntze
2015-12-12 19:22 ` Noel Kuntze
2015-12-12 19:38 ` Pablo Neira Ayuso
2015-12-12 19:34 ` Dâniel Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566cb640.46dc0d0a.5c3cc.287a@mx.google.com \
--to=fragabr@gmail.com \
--cc=fw@strlen.de \
--cc=jengelh@inai.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=linuxliste@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=noel@familie-kuntze.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).