Bonding Information: Difference between revisions
Content deleted Content added
| (4 intermediate revisions by the same user not shown) | |||
| Line 16: | Line 16: | ||
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]]. |
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]]. |
||
=Advantages= |
|||
More bandwidth, as well as resilience (having more that one line increases the probability of staying online in the event of a fault) |
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. |
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. |
||
=Packet re-ordering and lines with different latencies= |
|||
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. This can be overcome to some extent by adding/removing 'interleaving' on the ADSL lines. Latency can be easily seen on the CQL graphs for your lines on the ADSL [[:Category:Control Pages|Control Pages]]. |
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. This can be overcome to some extent by adding/removing 'interleaving' on the ADSL lines. Latency can be easily seen on the CQL graphs for your lines on the ADSL [[:Category:Control Pages|Control Pages]]. |
||
| Line 27: | Line 27: | ||
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. |
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. |
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. |
||
| Line 34: | Line 34: | ||
We provide email and text alerts of lines going off line unexpectedly so that you are alerted to the problem. |
We provide email and text alerts of lines going off line unexpectedly so that you are alerted to the problem. |
||
=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 |
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 FireBricks's at both sides will allow multiple tunnelled connections which can be via multiple lines that are even from different internet providers. |
||
=Equipment Required= |
=Equipment Required= |
||