Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Alex" <alexcos@nights.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] Multiple upload links on same eth
Date: Mon, 30 Aug 2004 22:07:45 +0000	[thread overview]
Message-ID: <002a01c48edd$d4e74760$6400a8c0@alex> (raw)

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

Hello..

I have a big problem and It seems I can't solve it..

Scenario:  Linux server , 2 eths  (one for Lan (eth0), one for Internet (eth1)).   I use NAT for LAN clients..

The internet eth is linked into a switch , along with 6 sdsl modems.. (256 kbit each link  -  most probably an htb on the other side)..

So , I made 6 aliases to my eth1 with ip's for the DSL connections .. ( 82.xx.xx.50 -> .56)

Now , how can I make some load balancing , in order to achieve a download rate of 256 * 6 kbit ?

I tried to use sch_teql , but seems that tc cannot work with aliases...

Anybody can help me here ?



Regards
    Alex

[-- Attachment #2: Type: text/html, Size: 1881 bytes --]

                 reply	other threads:[~2004-08-30 22:07 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='002a01c48edd$d4e74760$6400a8c0@alex' \
    --to=alexcos@nights.ro \
    --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