Aug 23 2022 09:31 AM
We have two ISP connections wired and wireless. Wireless is only used when wired goes down for both incoming and outgoing traffic. All our locations form 2 IPSEC tunnels across each connection separately. On failure traffic would shift from wired to wireless on Hub site and on remote site traffic is routed over tunnel formed over wireless connection. This happens using monitor attached to the static route which senses remote wired connection failed and removes the route from its routing table. And the next best is the wireless route determined by assigned Administrative Distance.
How can we achieve same/similar function with Azure Virtual Network Gateway Site to Site connections. When ever wired goes down we lose connectivity with Azure. We want the second tunnel to take over only after first has failed.
Aug 23 2022 11:28 AM
There can be multiple S2S connections to a Virtual Network Gateway in Azure. But it would depend on how traffic is routed.
If using a hardware firewall with the S2S tunnel as the on-prem endpoint, the firewall itself would need to know to choose the wireless route as its next hop once the old route is retracted, such as via BGP or dual-WAN.
Another way is to use a Windows Server as the S2S endpoint via the RRAS role. This box could be connected to your Wireless segment, for example, where it could be listed as a gateway route for the defined network traffic on that subnet.
Please like or mark this thread as answered if it's helpful, thanks!
Aug 23 2022 01:10 PM
Aug 23 2022 11:25 PM