All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luciano Ruete <luciano@lugmen.org.ar>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 2.6.17 kernels and equalize patch
Date: Fri, 19 Jan 2007 15:37:54 +0000	[thread overview]
Message-ID: <200701191237.54988.luciano@lugmen.org.ar> (raw)
In-Reply-To: <Pine.OSF.4.10.10701191201140.26328-100000@tiran.atnet.com.al>

On Friday 19 January 2007 08:13, hhoxha wrote:
> Hi
> Everybody in the list
>
> I have a situation like this
>
> ------        (IP1)
> linux  |----eth0.40------ |
> router |		  |	 |
> box    |     (IP2)        |------|Client Router ( Destiantion Net DNET)
>
>        |----eth0.41------ |      |                    /27 subnet
>
> ------
>
>
> I just want to balance the load of bandwidth per packet based between the
> two vlan interfaces  to Client Destination network
> What i have done is :
>
> //////////
> bash#/sbin/ip route add equalize $DNET scope global nexthop via
> $IP1 dev eth0.40 weight 1 nexthop via $IP2 dev eth0.41
> weight 1
> /////////
> bash#ip route show $DNET
>
> $DNET equalize
>         nexthop via $IP1  dev eth0.40 weight 1
>         nexthop via $IP2  dev eth0.41 weight 1
>
> But the traffic towards the $DNET does not seem equalized at all
> It goes out allways to the same interface
>
> Is this a problem of route caching or the  equalize patch needs to be
> applied to 2.6.17 kernel , or then I am missing something  ???

Equalize is a patch for 2.4, it never get's mainline, and there is no 2.6 
version AFAIK.The iproute option is there, but without the patch does 
nothing.
-- 
Luciano
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2007-01-19 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 11:13 [LARTC] 2.6.17 kernels and equalize patch hhoxha
2007-01-19 15:37 ` Luciano Ruete [this message]
2007-01-19 16:22 ` Tomasz Chilinski

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=200701191237.54988.luciano@lugmen.org.ar \
    --to=luciano@lugmen.org.ar \
    --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.