12,270
edits
Category:Bonding: Difference between revisions
m
→Bonding
mNo edit summary |
m (→Bonding) |
||
|
=Bonding=
==Download Bonding==▼
==Fast failover==
It is important that when a line fails for any reason the service switches automatically to using the remaining lines. Our constant quality monitoring system means we are constantly monitoring every line and will be able to react to a failure of a line within 10 seconds. When a line goes out of service the routing of traffic can automatically switch to remaining lines.
When using multiple lines for redundancy this allows the fall-back line to come in to service very quickly. When being used for extra speed the failed line simple means less speed until the problem is resolved.
We provide email and text alerts of lines going off line unexpectedly so that you are alerted to the problem.
▲==Download Bonding for Faster Speed==
'''From the Internet to you.'''
AAISP use FireBrick FB6000 routers to manage ADSL connections. This manages the bonding of traffic from AAISP to your location.
Speed wise, the FB6000 will route based on the speed of the line - so if you have a 10M line and a 5M line, then the traffic will be weighted correctly (i.e. 1/3 on the 5M line, and 2/3 on the 10M line.)
==Upload Bonding for Faster Speed==
Upload bonding requires a device at your side to route IP packet up alternate lines.
Typically a FireBrick can do this, as well as provide fallback (not using a line that is down) and firewalling. AAISP staff can also configure the Firebrick for your lines for a nominal fee.
Linux is capable of doing both basic [[Linux upload bonding using multipath routing|upload bonding by multipath routing]]. It can also do [[Linux upload bonding using policy routing|sophisticated upload bonding using a combination of policy routing and firewall rules]].
==IP addressing and routing==
Our control pages allow you to adjust the IP routing on your lines. You can have multiple IP addresses on a login, and each can be set for routing to one or more lines. You can set each IP address block separately and can define backup routing.
The recommended set up is to use a FireBrick and multiple PPPoE modems or bridges. The FireBrick would have one WAN address over all of the lines, and either public Legacy IPv4 addresses on the LAN, or private address and NAT on the FireBrick. In either case you can have public IPv6 addresses on the LAN and still handle bonding down and up on multiple lines.
The alternative if to use separate routers. These would normally share a /29 interlink subnet and connect to some firewall or router within you network, routing a static IP block to that router. The interlink address block could be private IPv4 addresses but you do not want NAT or fire-walling on the external routers even in that case as it will not handle the bonding. In general using the FireBrick and PPPoE is simpler and more flexible.
=Tunnelled bonding=
Another approach is to use a tunnelling system of some sort such as a VPN or FireBrick tunnels to tunnel traffic via one or more lines to a tunnel endpoint held in a data centre. We offer hosting services and host FireBricks as tunnel endpoints. Using FB2700's at both sides will allow multiple tunnelled connections which can be via multiple ADSL lines that are even from different internet providers.
=Examples=
| |||