From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
"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 17:03:56 +0100 [thread overview]
Message-ID: <496F5E6C.3030703@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0901151658280.17559@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Thursday 2009-01-15 16:54, Patrick McHardy wrote:
>>>> 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.
>>> But is there an equivalent user tool and interface at this time
>>> to obtain the same information?
>> No that I know of, but that doesn't matter as long as nobody has a
>> need for it.
>>
> As a developer of Xtables modules I have a need ;-)
That was one of my first thoughts, it looks mainly useful for
developers. And I'm not very fond of the idea of adding almost
300 lines of segfile beauty for that.
next prev parent reply other threads:[~2009-01-15 16:03 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
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 [this message]
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=496F5E6C.3030703@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=nowhere@hakkenden.ath.cx \
--cc=pablo@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 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).