Just following up on my rather old post -- but it took about three
months to go from wanting it to getting everything provisioned.
I'm running two ADSL lines with Linux doing interface bonding on the
(bridged) PPPoE ADSL; the ISP is doing some kind of similar bonding at
their end, although I suspect on Cisco hardware, not Linux.
Performance seems decent -- prior to this I was getting around 4.5 to
5 mbit down, 0.6mbit up via Exetel on Optus hardware.
With the two new lines (Telstra) I'm getting total 9.5 mbit down and
1.6 mbit up via IIG on Annex M AAPT hardware.
(Performance tested with the not-super-accurate-but-standard speedtest.net
(Refreshing the landlines helped -- definitely gained 500-1000 kbit
per line prior to bonding, perhaps just due to the cables being
re-crimped at both ends.. who knows)
Whether it actually turns out to be reliable in the long run, I'll
see... I do get HA in effect, as if one line goes down, all traffic
goes over the other after a fraction of a second delay.
The actual bonding stuff in Linux (Ubuntu LTS) was a bit fiddly to
configure -- the /etc/network/interfaces.d stanzas for bonding are
really only designed to work with ethernet ports or similar, that are
up instantly. To make it work automatically with pppd, I needed to
define the bond0 interface as having zero slaves, and then add a
script to /etc/ppp/ip-up.d/ which calls ifenslave -f bond0
(if the IP address matches one of those from my ISP)
On 28 March 2014 14:51, Toby Corkindale <toby(a)dryft.net> wrote:
Does anyone have real-world experience of using linux's interface
bonding on public networks?
(In the bandwidth-aggregation mode, not the redundancy mode)
I was wondering how I could make the following setup work:
* Rent a VPS in Melbourne with four IP addresses
* Get four (or just two) ADSL connections wired up to home
* Have your VPS connect four VPN connections from itself back to each
of your home IPs.
* Bond all four interfaces together
* Create a fifth VPN connection, this time going over the
bonded-virtual-interface between VPS and home, and then configure your
home server to use that link as the default route?
It sounds pretty messy and I'm not sure it'd actually work in
practice; the routing tables would be hell to get right.
Are there any guides already out there?
Turning and turning in the widening gyre
The falcon cannot hear the falconer
Things fall apart; the center cannot hold
Mere anarchy is loosed upon the world