From: Madhuri Patwardhan <madhuri@cc.iitb.ac.in>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bandwidth shaping over multiple WAN links
Date: Tue, 29 Jul 2003 04:53:50 +0000 [thread overview]
Message-ID: <marc-lartc-105945443015501@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105921202013273@msgid-missing>
Hi,
Thanks for the response.
> For download, you
> can use 3 links but only if you NAT and you have a lot of connections so you
> can load balance the different connections (like http traffic).
Can you provide some pointers on how to do this, especially load balancing?
Thanks,
Madhuri
> An ftp
> download, will only use 1 link.
> This all to say that's not so easy to determine what will be the maximum
> bandiwdth a class can get. And that's one of the parameters you need to
> create a good tc setup. But you can create a tc setup that can shape the 3
> links in both directions. Even if this shaping is not perfect, it still
> beter then not shaping at all.
>
> 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/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-29 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 9:47 [LARTC] bandwidth shaping over multiple WAN links hare ram
2003-07-26 9:51 ` madhuri
2003-07-26 10:54 ` Madhuri Patwardhan
2003-07-26 11:36 ` hare ram
2003-07-27 6:16 ` S Mohan
2003-07-28 17:43 ` Stef Coene
2003-07-29 4:53 ` Madhuri Patwardhan [this message]
2003-07-29 5:39 ` Martin A. Brown
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-105945443015501@msgid-missing \
--to=madhuri@cc.iitb.ac.in \
--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.