Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Does anybody work on supporting SPD matching Netfilter MARKS?
Date: Wed, 19 Jan 2005 13:58:59 -0500	[thread overview]
Message-ID: <20050119185859.GA12706@bender.817west.com> (raw)
In-Reply-To: <41EEAD74.4030804@protactive.nl>

On Wed, Jan 19, 2005 at 07:56:52PM +0100, Ludo Stellingwerff wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Thank for you reaction Jason,
> and sorry about the cross post, you're right, my mistake:(
> 
> The question I raised was not about the filtering side, but about the
> policy match. What NetBSD is capable of is to use it's packetfilter
> for deciding ipsec policies, by using a "tag".
> 
> In Linux terms this would mean that by using a firewall mark you could
> use the netfilter matching structure instead of the SPD internal matches.
> 
> spdadd mark 1 -P out esp/transport//require
> 
> This would read: All packages marked with firewall mark 1 should be
> encrypted and send on a transport mode ipsec connection.
> 
> Does anyone know some sort of implementation doing this?

ah--i misunderstood what you were asking.  i think your question is
probably better suited to the ipsec-tools list, as all you need
netfilter to do is set the mark, which it can already do.

-j

--
"It takes two to lie. One to lie and one to listen."
        --The Simpsons


  reply	other threads:[~2005-01-19 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19  6:44 Does anybody work on supporting SPD matching Netfilter MARKS? Ludo Stellingwerff
2005-01-19 14:41 ` Jason Opperisano
2005-01-19 18:56   ` Ludo Stellingwerff
2005-01-19 18:58     ` Jason Opperisano [this message]
2005-01-19 19:12 ` Lopsch

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=20050119185859.GA12706@bender.817west.com \
    --to=opie@817west.com \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox