From: Stephen Hemminger <shemminger@vyatta.com>
To: Andreas Henriksson <andreas@fatal.se>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/3] Add new (iptables 1.4.5 compatible) tc/ipt/xt module.
Date: Wed, 2 Dec 2009 08:58:41 -0800 [thread overview]
Message-ID: <20091202085841.1c37f49f@nehalam> (raw)
In-Reply-To: <59840ae567f82d81e66367eddea56553e0771e5f.1259765732.git.andreas@fatal.se>
On Wed, 2 Dec 2009 16:11:50 +0100
Andreas Henriksson <andreas@fatal.se> wrote:
> Add a new cleaned up m_xt.c based on m_xt_old.c
> The new m_xt.c has been updated to use the new names and new api
> that xtables exposes in iptables 1.4.5.
> All the old internal api cruft has also been dropped.
>
> Additionally, a configure script test is added to check for
> the new xtables api and set the TC_CONFIG_XT flag in Config.
> (tc/Makefile already handles this flag in previous commit.)
>
> Signed-off-by: Andreas Henriksson <andreas@fatal.se>
Will this still build on older versions? The iproute source is supposed
to build even with really old kernels and older iptables. It has
maintained source and binary compatibility.
--
next prev parent reply other threads:[~2009-12-02 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 15:10 [PATCH 0/3] iproute: fix tc ipt/xt module Andreas Henriksson
2009-12-02 15:11 ` [PATCH 1/3] Keep the old tc/ipt/xt module for compatibility Andreas Henriksson
2009-12-02 15:11 ` [PATCH 2/3] Add new (iptables 1.4.5 compatible) tc/ipt/xt module Andreas Henriksson
2009-12-02 16:58 ` Stephen Hemminger [this message]
2009-12-02 17:12 ` Andreas Henriksson
2009-12-02 15:12 ` [PATCH 3/3] Slightly improve the configure script Andreas Henriksson
2009-12-03 13:09 ` [PATCH 0/3] iproute: fix tc ipt/xt module jamal
2009-12-03 15:44 ` Andreas Henriksson
2009-12-26 19:18 ` Stephen Hemminger
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=20091202085841.1c37f49f@nehalam \
--to=shemminger@vyatta.com \
--cc=andreas@fatal.se \
--cc=netdev@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).