All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Samad <alex@samad.com.au>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] LoadBalancing on many asimetric different dsl's.
Date: Mon, 22 Jan 2007 12:41:54 +0000	[thread overview]
Message-ID: <20070122124154.GH3981@samad.com.au> (raw)
In-Reply-To: <20070122084928.10D7721C893@poczta.interia.pl>


[-- Attachment #1.1: Type: text/plain, Size: 4424 bytes --]

On Mon, Jan 22, 2007 at 01:21:32PM +0100, Jordi Segues wrote:
> >the above is actually covered in the wiki howto.  Bu tyou need to setup 
> >snat on
> >each interface, then connection tracking takes care of sending each stream 
> >out
> >the right interface, you need to use snat and not MASQ.
> 
> Great news :)
> And thankyou for the details.
> But could you give the link to the wiki howto?
> I only found old doc.
been a while since i had a look, quick google gave me this

http://lartc.org/howto/lartc.rpdb.multiple-links.html

I have this booked market as the wiki
http://linux-net.osdl.org/index.php/Main_Page

But I think the former is what you want

> 
> Thanks!
> 
> >
> >Then you need to setup up some ip rule tables for each of the interfaces.
> >
> >
> >my ip ru looks like this
> >
> >0:      from all lookup local
> >200:    from 144.132.145.38 lookup cable
> >201:    from 60.241.248.86 lookup adsl
> >32766:  from all lookup main
> >32767:  from all lookup default
> >
> >
> >my ip r sh tab default
> >
> >default  proto static  metric 5
> >        nexthop via 144.132.144.1  dev vlan2 weight 1
> >        nexthop via 10.20.20.230  dev ppp0 weight 20
> >default via 10.20.20.230 dev ppp0  src 60.241.248.86  metric 20
> >default via 144.132.144.1 dev vlan2  src 144.132.145.38  metric 30
> >
> >
> >This works fine for me, I have tracked packets with tcpdump on both the 
> >server
> >and the client.
> >
> >Alex
> >
> >
> >
> >>
> >> Thanks!
> >>
> >> Jordi Segues
> >>
> >> On 22 Jan 2007 09:49:28 +0100, sAwAr <sawar@interia.pl> wrote:
> >> >Hi,
> >> >
> >> >my company have just bought new network and I have question about one
> >> >problem.
> >> >As in topic we must use few completely different dsl's and balance 
> >traffic
> >> >between them.
> >> >2M/0,5M 4Mb/0,5M 8M/0,5M
> >> >M=Mb/s
> >> >I've never done such thing before so I have doubts how it will work. If
> >> >the links are symmetric 2/2 4/4 8/8 there is no problem because with
> >> >weights I can compensate  the difference between them and achieve nice
> >> >results. But what in my situation?
> >> >My questions are: how to set load balancing to get all links equally
> >> >loaded and avoid situation when the up load will be full and download
> >> >almost empty? I believe this situation can happen due to fact that load
> >> >balancing is based on flows and for example p2p or smpt/pop3 will eat
> >> >whole upload.
> >> >If my problem isn't clear I'll try to explain it better later.
> >> >
> >> >
> >> >Thanks in advance.
> >> >Pozdrawiam
> >> >sawar
> >> >
> >> >----------------------------------------------------------------------
> >> >Wolne adresy pocztowe @interia.eu >>> http://link.interia.pl/f19e8
> >> >
> >> >_______________________________________________
> >> >LARTC mailing list
> >> >LARTC@mailman.ds9a.nl
> >> >http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> >> >
> >>
> >>
> >> --
> >> Jordi Segués Daina
> >> -------------------------------------------------------
> >> Andorra GSM: (+376) 35 35 68
> >> France GSM: (+33) (0)6 81 88 35 55
> >> E-m@il / MSN: jordisd@gmail.com
> >> AIM: superjordix
> >> Skype: callto://superjordix
> >> -------------------------------------------------------
> >> http://www.JordiX.com
> >> _______________________________________________
> >> LARTC mailing list
> >> LARTC@mailman.ds9a.nl
> >> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> >>
> >
> >
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.4.6 (GNU/Linux)
> >
> >iD8DBQFFtJ1/kZz88chpJ2MRAhGKAJ9xthAZnQ/ovr82sa/x5j4BFJGgWwCgvtWa
> >dS7qseaia3GnZK/n8szE98Y=
> >=zLpL
> >-----END PGP SIGNATURE-----
> >
> >
> >_______________________________________________
> >LARTC mailing list
> >LARTC@mailman.ds9a.nl
> >http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> >
> >
> >
> 
> 
> -- 
> Jordi Segués Daina
> -------------------------------------------------------
> Andorra GSM: (+376) 35 35 68
> France GSM: (+33) (0)6 81 88 35 55
> E-m@il / MSN: jordisd@gmail.com
> AIM: superjordix
> Skype: callto://superjordix
> -------------------------------------------------------
> http://www.JordiX.com
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-01-22 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22  8:49 [LARTC] LoadBalancing on many asimetric different dsl's sAwAr
2007-01-22  9:03 ` Jordi Segues
2007-01-22 11:18 ` Alex Samad
2007-01-22 12:21 ` Jordi Segues
2007-01-22 12:41 ` Alex Samad [this message]
2007-01-23  0:11 ` sAwAr

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=20070122124154.GH3981@samad.com.au \
    --to=alex@samad.com.au \
    --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.