Split Access: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
The intended usage of multiple WAN feature: | The intended usage of multiple WAN feature: | ||
1) The RTU has two (or possibly more) ISP connections. Let there be network A and network B | 1) The RTU has two (or possibly more) ISP connections. Let there be network A and network B | ||
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). | ||
4) Failure of connection is detected via a pinger script. | 4) Failure of connection is detected via a pinger script. | ||
Revision as of 12:04, 25 May 2015
--Under construction--
Routing for multiple uplinks/providers
The intended usage of multiple WAN feature:
1) The RTU has two (or possibly more) ISP connections. Let there be network A and network B
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).
4) Failure of connection is detected via a pinger script.