From: Andreas Henriksson <andreas@fatal.se>
To: shemminger@vyatta.com
Cc: netdev@vger.kernel.org
Subject: [PATCH 0/3] iproute: fix tc ipt/xt module.
Date: Wed, 2 Dec 2009 16:10:37 +0100 [thread overview]
Message-ID: <cover.1259765732.git.andreas@fatal.se> (raw)
The xtables API has changed since the tc xt module was written.
This mini-series moves the legacy stuff out of the way (kept for
compatibility with older iptables versions) and starts
a new fresh xt module.
Hopefully the xtables api will be kept stable in the future.
If so, this new xt module should continue working since it only
uses exposed functions (unlike the old one which had an internal
header to access internal functions in xtables).
Andreas Henriksson (3):
Keep the old tc/ipt/xt module for compatibility.
Add new (iptables 1.4.5 compatible) tc/ipt/xt module.
Slightly improve the configure script.
configure | 93 ++++++++++--
tc/Makefile | 13 ++-
tc/m_xt.c | 161 +++++----------------
tc/m_xt_old.c | 433 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 557 insertions(+), 143 deletions(-)
create mode 100644 tc/m_xt_old.c
next reply other threads:[~2009-12-02 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 15:10 Andreas Henriksson [this message]
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
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=cover.1259765732.git.andreas@fatal.se \
--to=andreas@fatal.se \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).