All of lore.kernel.org
 help / color / mirror / Atom feed
From: RoMaN SoFt / LLFB!! <roman@madrid.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Tricking routes to load balance + transparent proxying?
Date: Fri, 23 Mar 2001 08:35:12 +0000	[thread overview]
Message-ID: <marc-lartc-98533644215923@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98519249805520@msgid-missing>

On Thu, 22 Mar 2001 09:24:18 +0100, you wrote:

>On Wed, 21 Mar 2001 21:31:28 +0100, you wrote:

>/usr/sbin/ip route add default \
>                nexthop dev eth0 via 192.168.0.229 onlink \
>                nexthop dev eth0 via 192.168.0.230 onlink
>
> Note I've removed the "equalize" option. Anyway I think this option
>does NOTHING if you don't patch your kernel so it should be the same
>having it or not.

 I've left the "onlink" option because I don't know which really does.

> As I said this converts my machine in a load balancer based on (src
>ip, dst ip) pair.
>
> The problem is squid which always use the same IP for ALL
>connections. This breaks my balance :-(

 Well, thinking more deeply, it shoudn't break balance because dst ip
changes with each connection (to a different site, of course). But
anyway I'm not getting the expected results. Sometimes during a
period (2-3 mins, eg) all connections (different dst sites included)
are routed via gateway1, and the other periodod all again are routed
via gateway2. It's strange. In other times when I've made 5 pings to 5
differents sites they are routed alternatively via the two gateways,
which is the expected behaviour. It's strange. It seems to work or
don't work randomly... That's the reason I though squid was the
guilty, but I realized that the balance should work...

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    ** RoMaN SoFt / LLFB **  
       roman@madrid.com
   http://pagina.de/romansoft
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

      parent reply	other threads:[~2001-03-23  8:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 16:37 [LARTC] Tricking routes to load balance + transparent proxying? RoMaN SoFt / LLFB!!
2001-03-21 19:10 ` Christian Worm Mortensen
2001-03-21 20:24 ` Jorge Boncompte [DTI2]
2001-03-21 20:31 ` Jorge Boncompte [DTI2]
2001-03-22  8:24 ` RoMaN SoFt / LLFB!!
2001-03-22 11:14 ` RoMaN SoFt / LLFB!!
2001-03-23  8:35 ` RoMaN SoFt / LLFB!! [this message]

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-98533644215923@msgid-missing \
    --to=roman@madrid.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 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.