netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Dâniel Fraga" <fragabr@gmail.com>
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 20:32:37 +0100	[thread overview]
Message-ID: <20151212193237.GB10759@salvia> (raw)
In-Reply-To: <566c4622.936d810a.ece67.ffffdfc9@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

On Sat, Dec 12, 2015 at 02:06:55PM -0200, Dâniel Fraga wrote:
> 	I tried this:
> 
> iptables -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
> 
> 	And I got the same error:
> 
> iptables: Protocol wrong type for socket.

There is some problem with the revision infrastructure.

iptables is asking for a match revision that is not available in the
kernel. So the negotiation between userspace and kernel to use a given
version of this match is failing for some reason.

Could you apply this patch and tell me what it shows when you run this
command and the one using -m state?

BTW, any particularly on your setup that is worth mention?

Thanks.

[-- Attachment #2: x.patch --]
[-- Type: text/x-diff, Size: 472 bytes --]

diff --git a/libxtables/xtables.c b/libxtables/xtables.c
index f14d503..d0e942c 100644
--- a/libxtables/xtables.c
+++ b/libxtables/xtables.c
@@ -825,6 +825,8 @@ int xtables_compatible_revision(const char *name, uint8_t revision, int opt)
 
 static int compatible_match_revision(const char *name, uint8_t revision)
 {
+	printf("compatible_match_revision name=%s revision=%u\n",
+		name, revision);
 	return xt_params->compat_rev(name, revision, afinfo->so_rev_match);
 }
 

  reply	other threads:[~2015-12-12 19:32 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 [this message]
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
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=20151212193237.GB10759@salvia \
    --to=pablo@netfilter.org \
    --cc=fragabr@gmail.com \
    --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).