From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 639AD1381F3 for ; Sun, 26 May 2013 22:52:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BB2BCE0B93; Sun, 26 May 2013 22:51:55 +0000 (UTC) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 667EDE0AED for ; Sun, 26 May 2013 22:51:54 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id hi5so1115225wib.6 for ; Sun, 26 May 2013 15:51:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=hbd/HdH6VfJ2tjDYj2yp6wPlUedIMHzMKrrL/UTL3dw=; b=xjDWGR87J3aygcBbGF1UZuPEHJ9sZWOqt6vpJoFs6kGmrs38L2+ThrZrHxOBGtjeWu ZvAwcTPuJJj61xOXbG3e9Xx77Sd7bSLqxDSVjHF8PvQxV7BGIfdThNAyTmfzSAhS4VOn HwMa7x1RoYsp7osGdTiyQ0jDRNKCMaZlB8oLZw3hvJepRzYKUF8ZALkb/beWLoGKqIZ5 KOWTJJTPpksUhvX8EP36KcPpQ8C4ihby+ybOxw9UvVyHLjpiKzDkOA4zl5lZHRb4JNyP 6lTdLktZ+Rn5YU1IUFcU+7g3IVsNsp3oAfdtedLlbDaU9tTfu0ek9GOAazqgm6I+t4wV bHeg== X-Received: by 10.180.36.147 with SMTP id q19mr6381232wij.26.1369608712815; Sun, 26 May 2013 15:51:52 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id h8sm13649664wiz.9.2013.05.26.15.51.51 for (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 15:51:52 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] IP Load Sharing - Per Packet Load Balancing (Linux router) Date: Sun, 26 May 2013 23:51:28 +0100 User-Agent: KMail/1.13.7 (Linux/3.8.13-gentoo; KDE/4.10.2; x86_64; ; ) References: <93dac986370ca717e03ae508d81d1173.squirrel@www.antarean.org> In-Reply-To: <93dac986370ca717e03ae508d81d1173.squirrel@www.antarean.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3273222.SJoEjvIpkM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201305262351.41186.michaelkintzios@gmail.com> X-Archives-Salt: e8bc73eb-e6c5-4f75-a97f-49c4de65394d X-Archives-Hash: aa7e4b6cfcb743b3d3530cffd5972c19 --nextPart3273222.SJoEjvIpkM Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 26 May 2013 22:35:14 J. Roeleveld wrote: > > On 25 May 2013, at 22:26, Nick Khamis wrote: > >> ... As mentioned this > >> would be two separate DSL services, connected using separate bridges. > >> I think I am describing more of a link aggregation or bonding.... > >>=20 > >> Also assuming that the service providers support bonding of the links= =C2=85. > >=20 > > Here in the UK this is a somewhat common thing - there are a number of >=20 > ISPs which >=20 > > offer bonded xDSL services. > >=20 > > It's certainly possible to use a Linux router to manage such a > > connection, although I don't know the details. > >=20 > > http://www22.brinkster.com/findall/bondedcd.html > >=20 > > http://www.automatedhome.co.uk/reviews/adsl-bonding-how-to-and-revie > > w.html >=20 > Bonding network devices together is quite simple, but it needs to be > configured on both ends. > In other words, to merge 2 DSL-connections together using bonding, you > need to get both from the same ISP and the ISP would need to support it on > their end. >=20 > If bonding can't be done on the ISP-side, you can use seperate > load-balancing/failover using other techniques. There's different ways of going about it, without or without MLPPP, dependi= ng=20 on what your ISP offers: http://wiki.aa.org.uk/index.php/Linux_upload_bonding_using_multipath_routing http://wiki.aa.org.uk/index.php/Linux_upload_bonding_using_policy_routing It used to be the case that Cisco 1800/2800 routers were used at customers'= =20 premises for MLPPP with certain UK ISPs, but since BT started implementing= =20 21CN (ADSL2+) they are using ERX core routers (Juniper) and no longer suppo= rt=20 MLPPP. I understand that MPLS is used instead these days, but have no=20 experience in its implementation. =2D-=20 Regards, Mick --nextPart3273222.SJoEjvIpkM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAABAgAGBQJRopH9AAoJELAdA+zwE4YetF4H/1b+IrCaY5L0YLBQ5QvdxGyE ZGuz5yk4SoF2KlYjjRvXE9znSGBUNbHFhQP/gzNPoKQ6Rr18CCPzZ3GwoN/vtpt9 d+Mb6vwxyea2c1zjO8LRndmVAnWVTrnFPmCgy0qHVIbM8gh0/LX3re7UdehR9Mqh +76O62sgsa+MIzyWVUe1gN6m5oL0ZEqcEYHPLx/Ql4f1neWH7zyqK+ZS/xheY0p2 NJc/XRb2Tj2gOd2xnWuXoXDhJj2VLPqmDs8tkWJDKwC5qXC9Gv1mXhbx1IfMq/Wv WHy9AcBl+9pWLEJN8pcdoEaO8cCYJknUpBFJnM3gdFDGgybPNuWQ0WBZgIiSjpE= =mmSa -----END PGP SIGNATURE----- --nextPart3273222.SJoEjvIpkM--