From: Daniel Lopes <lopsch@lopsch.com>
To: netfilter@lists.netfilter.org
Subject: Re: event sequence: QoS + 2.6sec ?
Date: Wed, 10 Aug 2005 17:26:32 +0200 [thread overview]
Message-ID: <42FA1CA8.7050303@lopsch.com> (raw)
In-Reply-To: <20050810115559.GA12617@pog.tecnopolis.ca>
Trevor Cordes schrieb:
> I'm using HTB QoS and 2.6sec (native 2.6 ipsec w/setkey) simultaneously.
> What is the sequence of events for an outgoing packet? I'm thinking the
> 2.6sec gets applied dead last, after the QoS scheduling has been done? Or
> does QoS get applied twice for a 2.6sec packet because it goes through
> egress twice?
>
> I could find no documentation on this subject, and it's actually quite
> important when using both together.
>
>
AFAIK Traffic Shaping is the last thing done before packet leaves into
the wire when applied on physical devices. But it depends on some
things. You can use for example IMQ. Then depending on the strategy
shaping is done before IPSec and before the shaping on the physical
device if you apply shaping on it. Take a look at the LARTC mailing
list. It's perhaps a better place for such questions.
prev parent reply other threads:[~2005-08-10 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 11:55 event sequence: QoS + 2.6sec ? Trevor Cordes
2005-08-10 15:26 ` Daniel Lopes [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=42FA1CA8.7050303@lopsch.com \
--to=lopsch@lopsch.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