Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
03-25-2021 07:05 AM
Dear all,
Please see the design below , the idea is testing against IPs 172.16.158.1 (IPs of VLAN 161) using path monitoring + static route
Can we add a path monitoring to an internal static route , that internal route monitoring reachability of 172.16.158.1 using as a source Interface a newly created loopback that we could associate with the GP gateway ?
The goal will be that when connectivity is lost from loopback to 172.16.158.1, the GP gateway will shutdown , the ultimate goal will be to avoid the mobile user traffic to reach the fw and then be black holed ...
Regards. -
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
