From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Art Emius <art@emius.ru>, netfilter@vger.kernel.org
Subject: Re: ipset issues
Date: Tue, 31 May 2016 12:25:05 +0200 [thread overview]
Message-ID: <20160531102505.GA2073@salvia> (raw)
In-Reply-To: <alpine.DEB.2.10.1605302116350.18831@blackhole.kfki.hu>
On Mon, May 30, 2016 at 09:19:34PM +0200, Jozsef Kadlecsik wrote:
> Hello,
>
> On Sat, 28 May 2016, Art Emius wrote:
>
> > This makes me feel confused, but seems it doesn't work at all. I've
> > tried both src,src and src,dst parameters. Still I see packets are being
> > dropped. But I use -i / -o in iptables rules it works fine.
>
> Sorry, I messed up the parameters.
>
> I think your kernel does not contain the patch
>
> commit ef5b6e127761667f78d99b7510a3876077fe9abe
> Author: Florian Westphal <fw@strlen.de>
> Date: Sun Jun 17 09:56:46 2012 +0000
>
> netfilter: ipset: fix interface comparision in hash-netiface sets
>
> ifname_compare() assumes that skb->dev is zero-padded,
> e.g 'eth1\0\0\0\0\0...'. This isn't always the case. e1000 driver does
>
> strncpy(netdev->name, pci_name(pdev), sizeof(netdev->name) - 1);
>
> in e1000_probe(), so once device is registered dev->name memory contains
> 'eth1\0:0:3\0\0\0' (or something like that), which makes eth1 compare
> fail.
>
> Use plain strcmp() instead.
>
> which went into the kernel v4.2. I assume it was not backported into older
> kernel releases.
This seems to apply cleanly against 3.2.x and 3.4.x.
I can request -stable submission for these two.
next prev parent reply other threads:[~2016-05-31 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 20:42 ipset issues Art Emius
2016-05-25 20:58 ` Jozsef Kadlecsik
2016-05-28 19:09 ` Art Emius
2016-05-30 19:19 ` Jozsef Kadlecsik
2016-05-31 10:25 ` Pablo Neira Ayuso [this message]
2016-05-31 11:05 ` Jozsef Kadlecsik
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=20160531102505.GA2073@salvia \
--to=pablo@netfilter.org \
--cc=art@emius.ru \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox