editor
698
edits
Category:Bonding: Difference between revisions
m
clean up, typos fixed: of it's → of its, ie → i.e. (2), etc → etc. (4), eg → e.g. (2), 10Mb/s → 10Mbit/s
m (clean up, typos fixed: of it's → of its, ie → i.e. (2), etc → etc. (4), eg → e.g. (2), 10Mb/s → 10Mbit/s) |
|||
|
=Overview=
AAISP support per-packet '''bonding''' - this is at the IP level, and simply means that packets entering or leaving your site use the ADSL lines on a roundrobin basis (or based on the speed of the lines). That way, a single TCP/IP session is transmitted over multiple lines.
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==
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.
==Limitations==
===FireBrick 105 Throughput===
We do recommend the FireBrick 105 product for bonding, fallback, and firewalling - as of Oct 2010, this is nearing the end of
-New products are due very soon to replace the 105.
IP blocks (configured on Clueless) can be routed to multiple lines on your login.
for fallback, the FB6000 will stop routing IPs down a line that is off line, and from the [[:Category:Control Pages|Control Pages]] you can control which lines are used.
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 (
==Upload Bonding==
*You have a block of IPs, big enough for your LAN
**The first usable IP will be Router 1, the second Router 2, and the rest will be for your devices.
*You have 2 standard ADSL routers (
**The ZyXELS can be configured to use the other router as a fallback gateway (giving some level of fallback if the ADSL goes down, this isn't configured automatically by AAISP router programming)
*You plug the routers, and computers etc. all in to the same network switch
*You pick on of the routers IP addresses to use as the gateway on your devices (or you can set up DHCP server on one of the routers)
**You could use one router as the gateway for half of your devices, and the other router as the gateway for the other half - thus giving some level of upload bonding
**The first usable IP will be Router 1, the second Router 2, and the rest will be for your firewall.
**The LAN block will be configured as static routes in the ADSL routers to route the traffic to your firewall.
*You have 2 standard ADSL routers (
**The ZyXELS can be configured to use the other router as a fallback gateway (giving some level of fallback if the ADSL goes down, this isn't configured automatically by AAISP router programming)
*You plug the ADSL routers and firewall (WAN port) in to the same network switch
*Your firewalls LAN port is connected to your main LAN switch.
*Your firewall uses one of the routers as it's gateway
*Your firewall can be the DHCP server, can run NAT etc. for your LAN
With this case, assuming your firewall is not able to do upload bonding, or have the ability to change which router it uses in the case of an ADSL line being down, in the event of the ADSL line that is being used for upload fails, fallback would need to be controlled manually (
==Full Bonding with a FireBrick==
| |||