05-02-2013 03:39 PM
Hi all,
I have this kind of setup and I can't figure out how this router thinks.
My setup uses Dual Wan in load balancing mode. I only need a single VPN tunnel. High availablity is my concern.
Site 1 has Fiber and Cable
Site 2 has Cable and FTTN
Every ISP supplies Static IPs
VPN works great in the event of an outage. I am still disappointed that it works in case a single primary WAN breaks, but is not operational if primary WAN on Site 1 shutdowns at the same time Site 2 secondary WAN stops. It's a really rare case but could happen.
Anyway, my problems lie where I need Protocol Binding to preserve secure WEB sessions (https, banking, supplier portal).
I have to bind, at least, port 443 to my primary WAN. This way, I can access websites and keep my session active.
Then, if I have to browse a HTTPS server on the other side of the VPN, Protocol Binding still tries to pass port 443 through WAN1. It does not even consider the VPN as a valid route first.
Problem (Maybe) Can I reduce Hop Count for Site 2 to less than 35?? P.S. I replaced addresses as I do not feel they are revelant.
| ||||||||||||||||||||||||||||||||||||||||
|
Thanks to all,
Bruno
Solved! Go to Solution.
05-08-2013 01:00 PM
I would conclude that is a bug and requires further investigation. I wouldn't call it a limitation if it were my decision (not that I matter so much in this regard)
-Tom
Please mark answered for helpful posts
05-08-2013 08:35 AM
Hi Bruno, in the event of a WAN failure, the protocol bind rules should be failing over to the other WAN port. That is how the router is intended to work.
If your contention is that it is not happening a few steps to do first to receive proper support-
*Upgrade to the latest firmware
*Factory default the unit
*Create the base configuration
*Test
If this fails under the most fundamental circumstance then it would be a good time to call the small business support center and ask for an investigation.
-Tom
Please mark answered for helpful posts