Comments
-
Hello Bruce, The policy on site B didn’t work. However, the test with the VPN bridge mode was successful. To apply restrictions to VPN users, it was necessary to add the range in the policies and use the deny option.
-
None of VPN client can reach with ping for 172.16.111.254 or 172.16.110.254. Ok, I will test this. Thank You.
-
Bruce, Yes, the route uses the same network gateway as site A. Routes in Firebox at site B: 172.16.111.0/24 > 172.16.110.254 - OK, bridge working. 172.16.113.0/24 > 172.16.110.254 - The tracert packet stops at this gateway 172.16.110.254. Route in Firebox at site A: 172.16.110.0/24 > 172.16.111.254 - OK, bridge working.…
-
Hello Bruce, Is it necessary to force the connection through the tunnel for this routing to work using the “Route VPN Traffic” option? The “Bridge VPN Traffic” option seems to make more sense to us, as we have two Firebox M370s at each site, and the Bridge option is used between them by WatchGuard. What happens in the…
-
Hello Bruce, the force option is disabled. All addresses from site A and site B are configured, but even so, the VPN does not route the traffic. We noticed that the client connected to the VPN at site A cannot reach the bridge gateway IP. On site B, even with a route to the gateway IP, it did not advance to one of the next…