Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Laura Garlando <laura.garlando@acktel.com>
To: lartc@vger.kernel.org
Subject: [LARTC] balancing issues
Date: Fri, 30 Jan 2004 14:20:19 +0000	[thread overview]
Message-ID: <401A6823.8010409@acktel.com> (raw)

Hello!
I'd like to balance traffic from eth0 onto eth1 and eth2 going to 
different providers.
As suggested on LARTC-howto, I've downloaded latest Julian's route 
patches (kernel 2.4.24) and I've set up everything as described on 
http://www.ssi.bg/~ja/nano.txt (nano-howto).
eth0 is the internal interface and eth1, eth2 are the interfaces 
connected to Internet.
The traffic doesn't get balanced with equal weights: most of it is 
always routed on eth1. I've also tried to give eth1 weight 1 and eth2 
weight 10 but nothing changes.
Where is the mistake?

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

                 reply	other threads:[~2004-01-30 14:20 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=401A6823.8010409@acktel.com \
    --to=laura.garlando@acktel.com \
    --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