Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Eric Leblond <eric@regit.org>
To: Harald Welte <laforge@netfilter.org>
Cc: Daniel Chemko <dchemko@smgtec.com>,
	netfilter@lists.netfilter.org,
	netfilter-devel@lists.netfilter.org, nufw-devel@nongnu.org
Subject: Re: A humble proposal
Date: Thu, 02 Oct 2003 23:26:12 +0200	[thread overview]
Message-ID: <1065129971.561.24.camel@porky> (raw)
In-Reply-To: <20031002195132.GA5758@sunbeam.de.gnumonks.org>

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

Le jeu 02/10/2003 à 21:51, Harald Welte a écrit :
> On Tue, Sep 23, 2003 at 09:13:21AM -0700, Daniel Chemko wrote:
> > I have seen some of this functionality in Checkpoint, and I think that
> > it would be immensely useful in the iptables community if it is adopted.
> 
> Just because a particular proprietary vendor offers a 'feature', it
> doesn't necessarrily mean that we need to do a blind copy of that
> feature.

I agree with you in the sense that we can do a better work. As I said
earlier in this thread and in this mailling list, the current tools
provided by Netfilter are great enough to build a good user
authentication system.

The NuFW project (http://www.nufw.org) has managed to build a user
authentication of packet, by (only) using libipq. We (the NuFW team)
think that in the current state of the project, we have managed to prove
the viability of the concept.

But, it's just the beginning ! With a slight modification of libipq and
of the corresponding module conbined with the use of CONNMARK, we should
be able to provide a user based marking of the connection.
If we're able to do so, the path to a user based ,QOS, bandwith sharing,
or even routing will be wide open.

We think that it's not a 'feature' but that it could really bring
something to the iptables community.

BR,
-- 
Eric Leblond
Nufw, Now User Filtering Works (http://www.nufw.org)

[-- Attachment #2: Ceci est une partie de message numériquement signée. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-02 21:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23 16:13 A humble proposal Daniel Chemko
2003-09-23 16:39 ` Eric Leblond
2003-09-23 21:10 ` Joel Newkirk
2003-10-02 19:51 ` Harald Welte
2003-10-02 21:26   ` Eric Leblond [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-24 10:57 A Humble Proposal John A. Sullivan III
2003-09-26  0:19 A humble proposal Daniel Chemko
2003-09-26  7:21 ` Eric Leblond
2003-09-26 11:53 A Humble Proposal John A. Sullivan III

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=1065129971.561.24.camel@porky \
    --to=eric@regit.org \
    --cc=dchemko@smgtec.com \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=nufw-devel@nongnu.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