Fabian,

Actually, what you're looking for is not link aggregation - link
aggregation works on level 2 and creates a virtual interface with a single
IP address. What you want is to have two routes to the same network (on
your case, the default gateway), each one with a single IP. This
configuration is known as multiwan or link balance, and involves playing
with ip route.

Good luck,
On Apr 8, 2016 14:03, "Jean Christophe André" <[email protected]>
wrote:

>         Hi everyone,
>
> Le 08/04/2016 11:53, Fabián Rodríguez a écrit :
>
>> I am wondering if anyone here has done network interface bonding[1]
>> using 2 x ADSL connections from the same provider?
>>
>> This is for a location where only Bell ADSL is available, and only at
>> 5Mbps. I am wondering if having 2 (or more) services at the same
>> location is possible (I am calling Bell) and if it would effectively
>> double (or at least increase) the bandwidth available when combined by
>> bonding network interfaces on a router appliance dedicated to that. I am
>> asking Bell if having 2 circuits at the same location would deliver
>> separate "guaranteed" 5Mbps or if it would be shared anyways.
>>
>> I've heard about this same scenario used with different providers to
>> ensure if one goes down service continues, but not with the same
>> provider twice. The goal here is not high availability, just higher
>> speeds.
>>
>> If anyone has other creative solutions to improve a link in such a
>> situation, I am listening :)
>>
>
> A few ideas to deal with low bandwidth in general:
>
> - configure (or enforce) DNS and web proxy/cache at the gateway => it will
> reduce the bandwidth load and thus enhance bandwidth availability
> => FLOSS solutions I'd use for that: bind or dnsmasq, squid, either
> iptables to enforce redirecting traffic to the proxy or using a "proxy.pac"
> for collaborative auto-proxy configuration
>
> - configure QoS at the gateway => sometime it's not that much about speed
> than about latency, for example people want to keep a good audio/video call
> quality while there is large downloads in progress ;
> => FLOSS solutions I'd use for that: iproute (tc and ip rule), iptables,
> shell scripting
> => most modern router equipment already have it, but sometime it's just
> not activated by default
>
> - tunnel all network traffic at the gateway to a network node you own, one
> with perfect bandwidth to your location (= you're able to get the top speed
> between them) and a higher bandwidth to Internet => compress the raw
> network traffic between your location and this node and you'll be able to
> get higher speed, at the cost of a bit more latency (won't be a problem if
> the network node is nearby, especially at the same ISP).
> => FLOSS solutions I'd use for that: OpenVPN with LZO compression (may be
> the easiest way), vde2 tunnels with compression, IPv6 link with IPcomp, …
>
> You may also mix multiple solutions, using for example iproute (ip rule)
> to redirect traffic accordingly.
>
> Cheers, J.C.
>
> --
> Jean Christophe ANDRÉ  —  Coordonnateur des infrastructures techniques
> Agence universitaire de la Francophonie (AUF)  —   http://www.auf.org/
> ✉ : AUF | 3034, boul Édouard-Montpetit | Montréal QC  H3T 1J7 | CANADA
> ℡ : +1 514 343 6630 #1568  ✦  ℻ : +1 514 343 2107
> ⎧Note personnelle: merci d'éviter de m'envoyer des fichiers Microsoft⎫
> ⎩Office, cf http://www.gnu.org/philosophy/no-word-attachments        ⎭
>
> _______________________________________________
> mlug mailing list
> [email protected]
> https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
>
_______________________________________________
mlug mailing list
[email protected]
https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca

Reply via email to