From: Alexander Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Classful Queuing
Date: Tue, 12 Oct 2004 07:05:53 +0000 [thread overview]
Message-ID: <20041012070553.GW522@samad.com.au> (raw)
In-Reply-To: <20041012010156.GY16095@cerberus>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Mon, Oct 11, 2004 at 10:46:01PM -0500, rsenykoff@harrislogic.com wrote:
> >But will the mark still exist after the encryption/encapsulation?
> >>not so about ingres, but the marking stay with the packet after the enc
> >>( well on 2.6 with native stack it does). I use this for marking
> >>packets.
>
> Isn't this going to depend on whether you are encrypting the whole packet
> (VPN style) or just the data portion of the packet (SSL style)?
I use it to mark parkets that are then esp enc. I am using in currently
with 2.6 and native ipsec stack to mark all packets that come in as esp
and then are de - enc, I allow these through the firewall. This was my
way around the old the problem of how to setup the firewall when the
ipsecX interface dissappeared.
I beleive the packet is encaped in place not duplicate. Then the new
packet is refeed back in to netfilter.
Alex
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-10-12 7:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 1:01 [LARTC] Classful Queuing Jamin W. Collins
2004-10-12 1:16 ` Alexander Samad
2004-10-12 1:31 ` Jamin W. Collins
2004-10-12 3:04 ` Alexander Samad
2004-10-12 3:46 ` rsenykoff
2004-10-12 6:25 ` Robert Felber
2004-10-12 7:05 ` Alexander Samad [this message]
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=20041012070553.GW522@samad.com.au \
--to=alex@samad.com.au \
--cc=lartc@vger.kernel.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.