In reply to a post by SimonMPFH:

There is no charge for bonding.
As long as the lines are on the same login they will bond automatically if you send a block of IPs to both lines in the control panel.

Nice feature to have without extra charge but reading the docs on their site, it sounds like the "free" aspect of it is more like load balancing than bonding. It would be interested to see what the HTTPx1 TBB speed test shows for an AAISP "bonded" line not using tunnel end points on each side of the link between you and AAISP.

In reply to a post by SimonMPFH:

If you have a FireBrick at each end you can to tunnel bonding, even over separate ISPs

Balance yes, no problem but I dont see how you can bond tunnels over separate ISPs. Did you mean bond two AAISP lines over two different AAISP backhaul providers? i.e. One AAISP line on Talk Talk Business back haul and one on BT Wholesale back haul. That would work as tunnel would be between you and AAISP.

Post removed as included a phone number and looked spammy

In reply to a post by awontroba:

I believe that true bonding does require support, probably with charge, at the ISP end.

We don't charge 'extra' for bonding. We have information and example router configurations on our support site: https://support.aa.net.uk/Category:Bonding

We're quite flexible, there are various ways of doing it, happy to help.

@craski - I do bonding, spreading the load over three lines, so even just one single TCP connection really goes at triple speed, true in either direction too. Works superbly. If one modem drops the link everything just carries on as AA for downstream and my own Firebrick router for upstream handle everything and reallocate the traffic to the remaining good links.

If you want to use mixture of ISPs I suppose it could be done using tunnelling with AA�s additional L2TP service, which then provides the real addressing and routing that the internet sees.

Indeed, I recently had bonding (second FTTC service) from AAISP and it works wonderful even for single threaded downloads or uploads. It maxes out both lines. Using an FB2900.

Edited by Ixel (Wed 09-May-18 19:28:00)

No joy configuring the EdgeRouter to do the bonding?
Firebricks are interesting but are pretty expensive.

I got it working on the EdgeRouter but not completely. To maximise the upstream I can't just have a single threaded upload. Otherwise it worked other than that. Firebrick handles it much better.

Currently bonding with AAISP FTTC using a RouterBoard. RouterOS can do the upstream per-packet round-robin using a firewall mangle rule. Works fine for a single session and achieves 36 megabit.

Have used various kit, Cisco IOS can do the upstream per-packet.
JunOS can only do it per session with a Layer 4 hash (like your EdgeRouter).

No fees as others have said, just setup the routing in the Control Pages.

Edited by deleted (Thu 10-May-18 09:30:20)

We've got some information about configuring other devices for bonding - https://support.aa.net.uk/Category:Bonding - but not the edge router. Bonding the download and fail-over is done at our end and will work if you only have a pair (or more) of simple DSL routers. I'ts the bonding and fail-over of the upload that a more sophisticated router will be needed for.

The price of the newly launched FireBrick 2900 is a couple hundred pounds cheaper than the previous 2700 model.