Simple bonding: Difference between revisions
m (punctuation, typos) |
mNo edit summary |
||
Line 1: | Line 1: | ||
<indicator name="Front">[[File:Menu-bonding.svg|link=:Category:Bonding|30px|Back up to the Bonding Page]]</indicator> |
|||
==Simple Download Bonding== |
==Simple Download Bonding== |
||
This is a poor-man’s bonding setup, but would be effective, but not as flexible is using additional hardware such as a Firebrick. As AAISP manage download bonding, the simplest set up is as follows: |
This is a poor-man’s bonding setup, but would be effective, but not as flexible is using additional hardware such as a Firebrick. As AAISP manage download bonding, the simplest set up is as follows: |
Latest revision as of 09:29, 19 March 2018
Simple Download Bonding
This is a poor-man’s bonding setup, but would be effective, but not as flexible is using additional hardware such as a Firebrick. As AAISP manage download bonding, the simplest set up is as follows:
- You have two or more ADSL lines with AAISP (either BT, or TT, or a mix)
- 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 two standard ADSL routers (e.g. supplied by AAISP)
- 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 one of the routers’ IP addresses to use as the gateway on your devices, or you can set up a 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
With this setup, you wouldn't have any firewall capabilities (apart from that provided by your operating systems.)
Simple Download Bonding, using a router/firewall
If you have an existing router/firewall, then you could use this to firewall your network, and provide NAT (if that's what you want to do). The points are similar to the above example, with a difference on the LAN side of the ADSL routers.
- You have 2 or more ADSL lines with AAISP (either BT, or BE, or a mix)
- You have a block of IPs, big enough for your LAN (assuming you are not natting), and a block of IPs for the ADSL routers and your firewall.
- 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 (e.g. supplied by AAISP)
- 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 firewall’s LAN port is connected to your main LAN switch.
- Your firewall uses one of the routers as its gateway
- Your firewall can be the DHCP server, can run NAT etc. for your LAN
In this case, assuming your firewall is not able to do upload bonding, and does not have the ability to change which router it uses in the case of an ADSL line being down, in the event that the ADSL line that is being used for upload fails, fallback would need to be controlled manually (i.e. by configuring the firewall to use the other ADSL router as its gateway)