Split Access: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
==This article is under construction== | |||
==Split Access== | |||
[http://lartc.org/howto/lartc.rpdb.multiple-links.html Routing for multiple uplinks/providers] | [http://lartc.org/howto/lartc.rpdb.multiple-links.html Routing for multiple uplinks/providers] | ||
The intended usage of multiple WAN feature: | ==The intended usage of multiple WAN feature:== | ||
1) The RTU has two (or possibly more) ISP connections. | 1) The RTU has two (or possibly more) ISP connections. | ||
2) One of the connections is active (primary), the other one is inactive (secondary). | 2) One of the connections is active (primary), the other one is inactive (secondary). | ||
3) If the primary connection fails, the RTU will switch to the secondary connection (i.e change the default gateway). | 3) If the primary connection fails, the RTU will switch to the secondary connection (i.e change the default gateway from primary gateway to secondary gateway). | ||
4) Failure of connection is detected via a pinger script. | 4) Failure of connection is detected via a pinger script. | ||
Latest revision as of 12:06, 25 May 2015
This article is under construction
Split Access
Routing for multiple uplinks/providers
The intended usage of multiple WAN feature:
1) The RTU has two (or possibly more) ISP connections.
2) One of the connections is active (primary), the other one is inactive (secondary).
3) If the primary connection fails, the RTU will switch to the secondary connection (i.e change the default gateway from primary gateway to secondary gateway).
4) Failure of connection is detected via a pinger script.