From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
netdev <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org,
Jesper Dangaard Brouer <brouer@redhat.com>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH nf-next] netfilter: xt_socket: add XT_SOCKET_NOWILDCARD flag
Date: Tue, 4 Jun 2013 11:10:14 +0200 [thread overview]
Message-ID: <20130604111014.73c718f7@redhat.com> (raw)
In-Reply-To: <1370300249.24311.190.camel@edumazet-glaptop>
On Mon, 03 Jun 2013 15:57:29 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> xt_socket module can be a nice replacement to conntrack module
> in some cases (SYN filtering for example)
>
> But it lacks the ability to match the 3rd packet of TCP
> handshake (ACK coming from the client).
>
> Add a XT_SOCKET_NOWILDCARD flag to disable the wildcard mechanism
Sorry, but I'm not sure I understand your description.
What is the effect of adding the XT_SOCKET_NOWILDCARD flag?
It almost sound like it adds the ability to match the 3rd packet of TCP
handshake (ACK coming from the client), is that the case?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2013-06-04 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 22:57 [PATCH nf-next] netfilter: xt_socket: add XT_SOCKET_NOWILDCARD flag Eric Dumazet
2013-06-04 9:10 ` Jesper Dangaard Brouer [this message]
2013-06-04 13:46 ` Eric Dumazet
2013-06-04 14:30 ` Jesper Dangaard Brouer
2013-06-20 8:38 ` Eric Dumazet
2013-06-20 9:55 ` Pablo Neira Ayuso
2013-06-20 10:19 ` Eric Dumazet
2013-06-20 12:52 ` [PATCH v2 " Eric Dumazet
2013-06-25 0:57 ` Pablo Neira Ayuso
2013-06-20 12:52 ` [PATCH iptables] xt_socket: add --nowildcard flag Eric Dumazet
2013-06-25 0:58 ` Pablo Neira Ayuso
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=20130604111014.73c718f7@redhat.com \
--to=jbrouer@redhat.com \
--cc=brouer@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--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.