netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dâniel Fraga" <fragabr@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: "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 21:31:47 -0200	[thread overview]
Message-ID: <566cae67.86f60d0a.f3ad2.2638@mx.google.com> (raw)
In-Reply-To: <20151212232044.GE12854@breakpoint.cc>

On Sun, 13 Dec 2015 00:20:44 +0100
Florian Westphal <fw@strlen.de> wrote:

> > 	Is there something missing?  
> 
> Yes: nf_conntrack_ipv4

	Thanks. This solved the problem.

	Any reason this module is necessary for kernel 4.3.1 and not
for 4.3.0? Maybe when the user compiles the state module, this option
should be marked automatically to prevent this, since state depends now
on nf_conntrack_ipv4 module.

-- 
Linux 4.3.2: Blurry Fish Butt
http://www.youtube.com/DanielFragaBR
http://exchangewar.info
Bitcoin: 12H6661yoLDUZaYPdah6urZS5WiXwTAUgL

  reply	other threads:[~2015-12-12 23:31 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 [this message]
2015-12-12 23:34                 ` Jan Engelhardt
2015-12-13  0:05                   ` Dâniel Fraga
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=566cae67.86f60d0a.f3ad2.2638@mx.google.com \
    --to=fragabr@gmail.com \
    --cc=fw@strlen.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).