All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Question about Bonding interfaces under Linux
Date: Thu, 27 Feb 2003 13:17:03 +0000	[thread overview]
Message-ID: <marc-lartc-104635186931005@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104634779325511@msgid-missing>


Jean-Philippe,

You do not want bonding.  Bonding joins together multiple physical
interfaces into a single logical interface with the same IP layer
characteristics.  You have two physical and logical interfaces over which
you wish to distribute your outbound traffic.

You want to configure split access load sharing. You will not reach
the total aggregate bandwidth for any single connection (download),
because each single connection will only be able to take advantage of one
of these uplinks.  The net effect, however, is that outbound traffic will
select one or the other link, spreading the entire load of the client
machines across both links.

This split access can be done dynamically (see nano.txt) or statically
(see adv-multi-internet.html).  In each case, the implementation involves
an understanding of the RPDB and use of multiple routing tables.

If you know the packet signature for each type of traffic you wish to send
across each link (maybe one is a higher quality connection), then you can
configure something like this:

  http://linux-ip.net/html/adv-multi-internet.html

If you wish to randomly select a link for each connection, see this:

  http://www.linuxvirtualserver.org/~julian/nano.txt

For a general introduction to the topic, see:

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

Good luck,

-Martin

 : I have a question about bonding 2 interfaces to 'load-balance' my 2
 : connections on Internet.
 : I have 2 differents Providers (and IP class) with dhcp addressing.
 : I tried a lot of things with ip+tc and also iptables, but nothing worked.
 : My question is how to set up my connection to be able to use both
 : interfaces to double my connection speed.
 :
 : My network is something like :
 :
 :                                                                  ________
 :                                           +------------+        /
 :                                           |            |       |
 :                             +-------------+ Provider 1 +------- 163.1.x.x
 : (dhcp)
 :         __                  |             |            |     /
 :     ___/  \_         +------+-------+     +------------+    |
 :   _/        \__      |     eth0     |                      /
 :  /             \     |              |                      |
 : | Local network -----+ Linux router |                      |     Internet
 :  \_           __/    |              |                      |
 :    \__     __/       |     eth1     |                      \
 :       \___/          +------+-------+     +------------+    |
 :                             |             |            |     \
 :                             +-------------+ Provider 2 +-------  82.18.x.x
 : (dhcp)
 :                                           |            |       |
 :                                           +------------+        \________
 :
 : Thanks.
 :
 : Jean-Philippe LE HENAFF
 : togusa@labo-unix.org
 :
 :
 :
 :
 : *************************************************************************
 : Ce message et toutes les pieces jointes (ci-apres le "message") sont
 : confidentiels et etablis a l'intention exclusive de ses destinataires.
 : Toute utilisation ou diffusion non autorisee est interdite.
 : Tout message electronique est susceptible d'alteration.
 : La SOCIETE GENERALE et ses filiales declinent toute responsabilite au
 : titre de ce message s'il a ete altere, deforme ou falsifie.
 : 				********
 : This message and any attachments (the "message") are confidential and
 : intended solely for the addressees.
 : Any unauthorised use or dissemination is prohibited.
 : E-mails are susceptible to alteration.
 : Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates
 : shall be liable for the message if altered, changed or falsified.
 :
 : *************************************************************************
 :
 : _______________________________________________
 : LARTC mailing list / LARTC@mailman.ds9a.nl
 : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
 :

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

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

      reply	other threads:[~2003-02-27 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 12:08 [LARTC] Question about Bonding interfaces under Linux jean-philippe.le-henaff
2003-02-27 13:17 ` Martin A. Brown [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-104635186931005@msgid-missing \
    --to=mabrown-lartc@securepipe.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.