All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Amin Azez <azez@ufomechanic.net>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Patrick McHardy <kaber@trash.net>
Subject: Re: new code; iptables-xml for iptables package.
Date: Fri, 10 Nov 2006 15:43:47 +0100	[thread overview]
Message-ID: <45549023.40801@netfilter.org> (raw)
In-Reply-To: <455311B5.5000600@ufomechanic.net>

Amin Azez wrote:
> (I hope these can be added to the standard iptables package)
> 
> Here is iptables-xml based on iptables-restore (as it knows how to parse
> iptables-save format), along with some xslt that converts back to
> iptables-save format.
> 
> A typical null use would be:
> 
>   iptables-save -c | iptables-xml -c | xsltproc iptables.xslt -

Just a wild thought, why not go further and provide a native XML 
interface instead of a converter?

BTW, could you also provide a DTD (Document Type Definition)? It can be 
interesting to check for well-formed documents.

-- 
The dawn of the fourth age of Linux firewalling is coming; a time of 
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris

  parent reply	other threads:[~2006-11-10 14:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 11:32 new code; iptables-xml for iptables package Amin Azez
2006-11-09 18:34 ` Patrick McHardy
2006-11-10 10:43   ` Amin Azez
2006-11-10 13:07     ` Patrick McHardy
2006-11-10 13:28       ` Amin Azez
2006-11-10 13:51         ` Patrick McHardy
2006-11-10 14:29           ` Amin Azez
2006-11-10 14:42             ` Patrick McHardy
2006-11-10 14:59               ` Amin Azez
2006-11-10 15:11                 ` Patrick McHardy
2006-11-10 15:57                   ` Amin Azez
2006-11-13 19:43                     ` Patrick McHardy
2006-11-10 14:43 ` Pablo Neira Ayuso [this message]
2006-11-10 15:13   ` Amin Azez
2006-11-22 17:37 ` Glen Turner
2006-11-23 12:55   ` Amin Azez

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=45549023.40801@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=azez@ufomechanic.net \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.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.