netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Attila Toth <panther@balabit.hu>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: kaber@trash.net, netfilter-devel@vger.kernel.org
Subject: Re: [PATCHv3 2/2][RESEND] Addrtype match extension: limit addrtype check on the packet's interface
Date: Fri, 16 Nov 2007 18:19:44 +0100	[thread overview]
Message-ID: <473DD130.8040601@balabit.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0711161747290.31083@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Nov 16 2007 16:30, Laszlo Attila Toth wrote:
>> Also it may be better if only the xt_addrtype remains and ipt_addrtype_info is
>> used for the old one and xt_addrtype_info for the new one. But it may be
>> confusing: ipt_* in the xt_* files...
> 
> Will be fixed 'one day' when all the compat code is removed :p

Not 'one': 'Mon' (Monday) :P

-- 
Panther

  reply	other threads:[~2007-11-16 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 17:14 [PATCHv3 0/2+1] Find address type on the packet's interface Laszlo Attila Toth
2007-11-15 17:14 ` [PATCHv3 1/2] Find address type on a specific or on any interface Laszlo Attila Toth
2007-11-15 17:14   ` [PATCHv3 2/2] Addrtype match extension: limit addrtype check on the packet's interface Laszlo Attila Toth
2007-11-15 17:14     ` [PATCHv3 iptables] Find address type on a specific or on any interface Laszlo Attila Toth
2007-11-16 14:22     ` [PATCHv3 2/2][RESEND] Addrtype match extension: limit addrtype check on the packet's interface Laszlo Attila Toth
2007-11-16 15:06       ` Jan Engelhardt
2007-11-16 15:30         ` Laszlo Attila Toth
2007-11-16 16:49           ` Jan Engelhardt
2007-11-16 17:19             ` Laszlo Attila Toth [this message]
2007-11-16 17:53               ` Jan Engelhardt

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=473DD130.8040601@balabit.hu \
    --to=panther@balabit.hu \
    --cc=jengelh@computergmbh.de \
    --cc=kaber@trash.net \
    --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).