netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Netfilter Core Team <netfilter-devel@vger.kernel.org>
Subject: Head up [was Re: [PATCH 0/4] ipset: add "inner" flag support]
Date: Wed, 29 May 2013 11:28:52 +0200	[thread overview]
Message-ID: <20130529092852.GA4081@localhost> (raw)
In-Reply-To: <51A54814.5040405@googlemail.com>

Hi Jozsef,

Cc'ing netfilter-core.

David has been pushing this guy to get him out of anonimity. According
to the kernel policy (Developer authenticity certificate), we need
contributions from a source that we can recognize to avoid legal
issues.

If the contributions are not worth, like that stupid variable rename
he made, better just not to risk and skip them.

Regards.

On Wed, May 29, 2013 at 01:13:08AM +0100, Dash Four wrote:
> This series of 4 patches implements "inner" flag option in the set
> iptables match, allowing matching based on the properties
> (source/destination IP address, protocol, port and so on) of the
> original (inner) connection in the event of the following
> ICMP[v4,v6] messages:
> 
> ICMPv4 destination-unreachable (code 3);
> ICMPv4 source-quench (code 4);
> ICMPv4 time-exceeded (code 11);
> ICMPv6 destination-unreachable (code 1);
> ICMPv6 packet-too-big (code 2);
> ICMPv6 time-exceeded (code 3);
> 
> 
> Dash Four (4):
>   ipset: minor variable-naming corrections
>   ipset: add "inner" flag implementation
>   iptables: add set match "inner" flag support
>   iptables (userspace): add set match "inner" flag support
> 
> 
> 

  reply	other threads:[~2013-05-29  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  0:13 [PATCH 0/4] ipset: add "inner" flag support Dash Four
2013-05-29  9:28 ` Pablo Neira Ayuso [this message]
2013-05-29 11:47   ` Head up [was Re: [PATCH 0/4] ipset: add "inner" flag support] Jozsef Kadlecsik
2013-05-29 11:51     ` Jozsef Kadlecsik
2013-05-29 16:38 ` [PATCH 0/4] ipset: add "inner" flag support 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=20130529092852.GA4081@localhost \
    --to=pablo@netfilter.org \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).