All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dâniel Fraga" <fragabr@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
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 17:35:58 -0200	[thread overview]
Message-ID: <566c7722.c17b810a.f320.0045@mx.google.com> (raw)
In-Reply-To: <20151212193237.GB10759@salvia>

On Sat, 12 Dec 2015 20:32:37 +0100
Pablo Neira Ayuso <pablo@netfilter.org> wrote:

> 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?
	
	Nothing special here. I'll try the patch and reply back. Just a
minute.

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

  reply	other threads:[~2015-12-12 19:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12  3:38 Linux 4.3.1 regression: -m state returns "Protocol wrong type for socket" Dâniel Fraga
2015-12-12  9:56 ` Remzi AKYÜZ
2015-12-12 10:18   ` Jozsef Kadlecsik
2015-12-12 11:50     ` Remzi AKYÜZ
2015-12-12 12:04       ` Jozsef Kadlecsik
2015-12-12 12:09         ` Noel Kuntze
     [not found]           ` <566C1751.403@gmail.com>
     [not found]             ` <566C1804.5060605@gmail.com>
2015-12-12 13:41               ` 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 [this message]
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-12 23:34                   ` Jan Engelhardt
2015-12-13  0:05                   ` Dâniel Fraga
2015-12-13  0:30                     ` Jan Engelhardt
2015-12-13  0:30                       ` Jan Engelhardt
2015-12-13  0:32                       ` Dâniel Fraga
2015-12-13  0:47                         ` Jan Engelhardt
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
2015-12-12 16:01   ` 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=566c7722.c17b810a.f320.0045@mx.google.com \
    --to=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 \
    --cc=pablo@netfilter.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.