From: Daniel Musketa <Daniel@musketa.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bypassing qdisc for some traffic
Date: Wed, 15 Nov 2006 15:43:10 +0000 [thread overview]
Message-ID: <200611151643.10569.Daniel@musketa.de> (raw)
In-Reply-To: <BAY103-DAV7E1AA9503C1DE9109CEB3B2EA0@phx.gbl>
> Problem: I don't want to limit traffic from eth1 to
> eth2. Is there a clean way to bypass the qdisc for
> certain kind of traffic (all traffic from eth1)?
You can create a 100mbit root class 1: rate 100mbit default 11, containing two
subclasses: 1:10 rate 2mbit and 1:11 rate 98mbit ceil 100mbit. Use iptables
to mark all traffic coming from eth0 to go to 1:10 ...
Daniel
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-11-15 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 15:21 [LARTC] bypassing qdisc for some traffic Marco Berizzi
2006-11-15 15:43 ` Daniel Musketa [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=200611151643.10569.Daniel@musketa.de \
--to=daniel@musketa.de \
--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.