From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping outgoing traffic over multiple devices
Date: Wed, 16 Oct 2002 09:48:01 +0000 [thread overview]
Message-ID: <marc-lartc-103476180110520@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103471240602360@msgid-missing>
On Wednesday 16 October 2002 15:11, raptor wrote:
> |Yes, the imq device. This is a virtual device (you can have more then
> | one) and you can add a qdisc to it. You can redirect packets to it with
> | iptables and this can be done on each interface and for in and outgoin
> | packets. In your case you have to create 1 imq device and redirect all
> | outgoin packets to it and shape the imq device.
> |More info http://trash.net/~kaber/imq/
>
> ]- does later packets go to the device they was directed in the
> begining.... i.e. if packet has to go out trought eth1 but i redirect it to
> imq, the flow is shaped to the desired bandwith but after that it continues
> its normal path.... i.e. flow become from this :
>
> eth0 <----> eht1
>
> this :
>
> eth0 <--> imq <--> eth1
I's more like
eth0 -> imq0 -> forwarding -> eth1
eth1 -> imq0 -> forwarding -> eth0
You can even do
eth0 -> imq0 -> forwarding -> imq0 -> eth1
One of the disadvantage is the delays. The packet will travel thru 2 queues.
So shaping on imq AND ethx is not such a good idea.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-10-16 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 20:05 [LARTC] Shaping outgoing traffic over multiple devices Sebastian 'spax' Pape
2002-10-15 20:20 ` Stef Coene
2002-10-16 6:18 ` raptor
2002-10-16 9:48 ` Stef Coene [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=marc-lartc-103476180110520@msgid-missing \
--to=stef.coene@docum.org \
--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.