All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jussi Norlund <jussi@greta.nu>
To: lartc@vger.kernel.org
Subject: [LARTC] Determining shape rate for multihomed route.
Date: Fri, 28 Feb 2003 10:45:49 +0000	[thread overview]
Message-ID: <marc-lartc-104642908726937@msgid-missing> (raw)

Hello,
I have a setup that looks like this:

|---------    |-----------------------|
| ADSL1  |----| Linux 2.4.20          |
|________|    | + static routes patch |     |-------|
              | + Masquerading        |-----| LAN   |
|---------    | + HTB on LAN egress   |     |_______|
| ADSL1  |----|_______________________|
|________|  /
           /
}-------| /
| ADSL3 |/
|_______|

I followed the "Nano-howto" to set up the load balancing and that seems to work just fine.

I have worked out some classes with HTB that would look nice for one external interface. I want to allow any lowpriority traffic to use all the bandwidth, from all three interfaces when nothing else is coming through.

Setting the shaping rate to the sum of ADSL1,ADSL2 and ADSL3 will (of course) not give satisfying results.

I would like to have some sort of shared rate between the external interfaces while still shaping on LAN egress (does this make sense). Preferably this would be combined with dead gateway detection, so that the $RATE cuts to half when one external interface is down.

Sending too much traffic out on one ADSL fills it's buffer and destroys latency, so I really do not wish for this to happen at all.

What would be the best way to determine the rate to shape at?

TIA,
Jussi Norlund
-- 
"To do is to be." - Socrates. "To be is to do." - Plato. "Skoo be do be do." - Sinatra.
1024D/805498C0
AC06 7251 B58B 7A3F 0168  758F 3252 F725 8054 98C0
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-02-28 10:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-104642908726937@msgid-missing \
    --to=jussi@greta.nu \
    --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.