netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Jan Engelhardt <jengelh@medozas.de>,
	"Nikolay S. Rybalov" <nowhere@hakkenden.ath.cx>,
	netfilter@vger.kernel.org,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: Troubles with MARK target in 2.6.28
Date: Thu, 15 Jan 2009 15:06:40 +0100	[thread overview]
Message-ID: <496F42F0.7050305@netfilter.org> (raw)
In-Reply-To: <496F40DC.2000605@trash.net>

Patrick McHardy wrote:
> Jan Engelhardt wrote:
>> But the spartanic output of those proc files barely helps (especially
>> in light of multiple revisions), so here is the patch I spoke about,
>> refreshed and rebased, that solves the worries.
> 
> That seems a bit overkill. Text-based representation also doesn't seem
> ideal, iptables already has this information and a cmdline user will
> simply use "iptables ... -h" to get the supported option. For other
> programs a binary representation would probably be easier to handle.

Agreed. The text-based interface seems to me like yet-another-interface
that users may (ab)use (like /proc/net/nf_conntrack, I have seen people
polling from it to display information, this was OK in the early days).
Following this basis, one may come and implement another text-based
interface to display the rule-set in the kernel and so on.

-- 
"Los honestos son inadaptados sociales" -- Les Luthiers

  reply	other threads:[~2009-01-15 14:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86617ABF8F494F2A940C18251E3DC8D0@Hakkenden>
2009-01-12  6:19 ` Troubles with MARK target in 2.6.28 Patrick McHardy
2009-01-12  7:08   ` Patrick McHardy
2009-01-12  7:15     ` Jan Engelhardt
2009-01-12  7:18       ` Patrick McHardy
2009-01-14  5:39         ` Jan Engelhardt
2009-01-15  8:06           ` Targets with "mangle" table limiting (Was: Re: Troubles with MARK target in 2.6.28) Jan Engelhardt
2009-01-15 12:08             ` James King
2009-01-15 13:47               ` Patrick McHardy
2009-01-15 16:44                 ` Jan Engelhardt
2009-01-15 22:38                   ` James King
2009-01-16  8:04                     ` Patrick McHardy
2009-01-18  7:32                       ` James King
2009-01-16  7:33                   ` Patrick McHardy
2009-01-16  8:15                     ` Jan Engelhardt
2009-01-16  8:19                       ` Patrick McHardy
2009-01-18  7:08                       ` James King
2009-01-19 14:29                         ` Patrick McHardy
2009-01-15 13:57           ` Troubles with MARK target in 2.6.28 Patrick McHardy
2009-01-15 14:06             ` Pablo Neira Ayuso [this message]
2009-01-15 15:51               ` Jan Engelhardt
2009-01-15 15:54                 ` Patrick McHardy
2009-01-15 15:58                   ` Jan Engelhardt
2009-01-15 16:03                     ` Patrick McHardy
2009-01-15 16:20                       ` Jan Engelhardt
2009-01-16  7:33                         ` Patrick McHardy
2009-01-16  8:14                           ` Jan Engelhardt
2009-01-12 18:12   ` Nikolay S. Rybaloff

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=496F42F0.7050305@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=jengelh@medozas.de \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=nowhere@hakkenden.ath.cx \
    /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).