lartc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zarkdav@eddy.easynet.fr (Benjamin Ryzman)
To: lartc@vger.kernel.org
Subject: [LARTC] Multipath routing with different bandwidth and cost
Date: Wed, 29 Jan 2003 11:04:51 +0000	[thread overview]
Message-ID: <marc-lartc-104383834415047@msgid-missing> (raw)

Hi,

My workstation is connected to a LAN with two different gateways. GW1 is
rate-limited to 2Mbps while GW2 is unlimited. Routing through GW1
is cheaper, thus I don't want to be using only GW2.

At any given time, I would like to be able to use GW1 while keeping it
uncongestioned and to use GW2 for the remaining traffic.

I know I can create a weighted multipath route but I believe the weight
doesn't allow me to specify the rate-limitation of GW1.

Do you think I can come to a solution using iproute2, netfilter and tc?

Regards,
Benjamin
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-01-29 11:04 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-104383834415047@msgid-missing \
    --to=zarkdav@eddy.easynet.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).