From: Eliezer Croitoru <eliezer@ngtech.co.il>
To: Ricardo Klein <klein.rfk@gmail.com>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: Help with Load Balancing
Date: Wed, 17 Jul 2013 00:00:07 +0300 [thread overview]
Message-ID: <51E5B457.5000704@ngtech.co.il> (raw)
In-Reply-To: <CADuigkViSbrbHoO_8-htS-6yRvEqi5MoRdB32N=MSexyjxS1Hg@mail.gmail.com>
You cannot do a Magic way of what you want but as Andrew stated you can
LB between two links.
What is the scenario you do have in hands??
iproute is a route level policy\rules.
If you would have a smarter system it would probably taken a snapshot of
the each uplink every specific interval and calculate the global usage
of the link balancing and would mark more connections based on the least
loaded connection.
From the admin perspective it could be something like "dont route using
uplink1 but use uplink2".
The above algorithm is pretty simple if you have uplink1 and uplink2
which you are not afraid both of them to be down.
Once you have the obstacle of "I'm afraid that the link will go down"
you can play with whatever routing you want since the user will not feel
it in most cases.
Eliezer
On 07/16/2013 06:23 AM, Ricardo Klein wrote:
> I think IPRoute is the one who should make the magic, but, if anyone
> can help me here, even pointing me in the right way....
>
> I know I can split my 2 connections in a static way, making lan subnet
> A go trough uplink 1 and lan subnet B trough uplink2, but, there is
> any way to make this "automatic" like "Hey iproute2, use the least
> used uplink to let users fly"
>
> I know, if user A is using uplink1 it should go trough that link until
> the end of the navigation, but, later in new requests he should be
> able to start the connection using uplink 2 if uplink 1 is starving.
>
> Is there any way to reach that with Linux?
>
>
> --
> Att...
>
> Ricardo Felipe Klein
> klein.rfk@gmail.com
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-07-16 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 3:23 Help with Load Balancing Ricardo Klein
2013-07-16 19:47 ` Andrew Beverley
2013-07-16 21:00 ` Eliezer Croitoru [this message]
2013-07-19 4:24 ` Ricardo Klein
2013-07-22 21:59 ` Eliezer Croitoru
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=51E5B457.5000704@ngtech.co.il \
--to=eliezer@ngtech.co.il \
--cc=klein.rfk@gmail.com \
--cc=netfilter@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