@NightShade1 wrote:
nope.. the private link its a point to point link that does not have nothing to do with the internet connection...
Private link at least for me its a link that you can buy to the ISP.
Physically the ISP install you a transiver in your branch and also install a transiver on the central site. Your data goes through the ISP network but never goes to internet.
Then you got ANOTHER transiver which leads you to the internet. You can loose the point to point private link but not ncesary the internet. In this site the client would like to use the internet as a backup link, that works automatically, for the wireless users.
So at the end there will cases in which the client will loose the private link but not the internet link in both sides.
Cheers
Carlos
What you want with WLAN is to make it deterministic and not complicated. Once you have to contend with failover/failback and timers between a public vs a private link, you make it more undeterministic.
Is there a level of uptime that is expected of this site?
Do your users expect the WLAN to be up when the point to point link is down?
What applications do you expect to continue to work when the point to point is up vs. when it is down?
What applications do you want to make available? Will IP addressing still work properly upon failover?
How will applications work if you decide to fail back?
What timers should you have in place to determine when the point to point is down and attempt to fail back when it is up?
Who will provide DHCP for devices upon failover?
If you just tie uptime of the WLAN to the point to point connection, everything is simpler and you do not have all of these questions to answer... If the point to point had some redundancy you would manage the entire site by the status of that, instead of having to contend with multiple issues created by redundancy and timers.