Link to home
Start Free TrialLog in
Avatar of bminetwork2277
bminetwork2277

asked on

Watchguard Additional Network cannot reach VPN networks

I have a watchguard X700 withsetup to use 172.16.0.0/24 on the trusted interface. I have several VPN tunnels setup to remote networks on the Watchguard, ex. 192.168.1.0/24. I have the ANY to ANY rule for these 2 networks and evertyhing works fine. On the Watchguard I added an additional network of 172.16.1.0/24 The watchguard acts as the default gateway for this network as 172.16.1.1. If I have a client on this network he can access the 172.16.0.0 network fine but not the Remote VPN network of 192.168.1.0/24. I assumed I need to add a route on the Watchguard and did this with no success. Has anyone done this before?

Thanks,
ASKER CERTIFIED SOLUTION
Avatar of chawcheskew
chawcheskew

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bminetwork2277
bminetwork2277

ASKER

The VPN endpoint in this case is A watchguard SOHO 6. It is setup to send traffic to 172.16.0.0/24 only. I figured I would add the route on one side and see if I can get a ping through. I will add it on the remote VPN device as well and test it.
Excellent.  The routing will definitely required for the ping response to be returned to you.