Bonding FireBrick

Back up to the Bonding Page
From AAISP Support Site


ADSL and FTTC lines can be bonded, typically A&A customers bond a BT and a TT line for greater resilience. Multiple FTTC lines can be bonded together too in the same way.

Staff are happy to help with any configuration.

Configuration

Basically, setting up a PPP entry for each of your lines and setting the speed will mean the lines will be bonded.

Example

Set up port 3 to connect to the second modem you have, i.e.:

<ppp port="WAN2" username="abc@a.2" password="secret" comment="BT ADSL" graph="BT ADSL 2" log="true"/>

and change the port from:

<port name="LAN3" ports="3"/>

to

<port name="WAN2" ports="3"/>

If you prefer, you can rearrange the ports so that they are in sequential order etc...

We now have:

  • Port 1 = LAN
  • Port 2 = Spare
  • Port 3 = ADSL Line 2
  • Port 4 = ADSL Line 1

Bond the PPPoE

Bonding on a 2700 requires the Bonding capability - found on the Fully-Loaded variants.

Simply setting speed=x in the ppp config will bond the PPPoE for uplink. The speed value is in bits per sec. You can use G/M/K when specifying the value, as well as B for bytes, or i, power of 2. e.g., 1000000 is the same as 1M)

e.g.:

<ppp port="WAN1" username="abc@a.1" password="secret" comment="BT ADSL" graph="BT ADSL" log="true" speed="1000000"/>
<ppp port="WAN2" username="abc@a.2" password="secret" comment="BT ADSL" graph="BT ADSL 2" log="true" speed="1000000"/>

Since each PPP connection will give the FireBrick a default route, the FireBrick will use both, and upload traffic on each ppp connection up to the speed given. The speed is in bits, so this example is where the upload is 1M. If the upload is different on the lines, then that's fine - e.g., you may have a line using Annex-A and one Annex-M. Setting the speed correctly will mean the correct amount of traffic will be sent up each line.