12,270
edits
Bonding Information: Difference between revisions
m
→Tunnelled bonding
mNo edit summary |
|||
| (13 intermediate revisions by 3 users not shown) | |||
|
=Overview=
One of the key benefits of our service is that downlink bonding can be achieved with nothing more than multiple cheap
MLPPP (Multilink PPP) Is not supported - it was originally designed for ISDN, and AAISP take the view that bonding at the IP level is the way to do bonding.
==Advantages==▼
==Download bonding==
Sending the packets to you over multiple lines is the job of the routers at AAISP, this is configured by the routing options on your IP addresses in the Control Pages
==Upload bonding==
Packets leaving your network is up to your own router. There are various routers which can do this, see [[:Category:Bonding Configuration]], or you can just use one line to send packets up without any special routers at all, see [[Simple bonding]].
More bandwidth, as well as resilience (having more that one line increases the probability of staying online in the event of a fault)
People often want greater upload bandwidth so as to improve performance of remote workers (etc. VPN/remote sessions etc.) or sending out large files etc.
As IP packets are taking separate routes to get to you, there is potential for packets to be out of order. This can happen where the ADSL lines have different amounts of latency.
In theory, out of order packets should not be a problem, TCP copes with out of order packets, but some applications may have problems. We have seen some VPNs and specific video streaming applications being very sensitive to packets being out of order. This is rare though.
Packets sent from AAISP to you take the line that has the lowest current delay. This is worked out by recent packets and the base latency of the line. Due to this you may see traffic preferring one of your lines over the other. The aim of this is to ensure packets arrive in order if possible. (Not that IP guarantees packet order.) In theory a full speed transfer should fill both lines, but slower traffic will have a bias to the low latency line.
==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.
We provide email and text alerts of lines going off line unexpectedly so that you are alerted to the problem.
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.
| |||