KCS1 
Zyxel Employee
Comments
-
Ended up being a corrupted default vpn security policy rule. Deleted, recreated, and all is well.
-
Thank you Zyman2008 although the static route unfortunately did not work either :(.
-
Update, when testing and try to ping a far end USG at 192.168.1.x the response comes back 34.31.X.X. Quite odd as we do not have 34.x.x.x anywhere in the system. Tier1 was lost as to why that was occurring.
-
Zyxel Tier1 support looked at the setup today and could not figure out why it was not working. They escalated the issue to US Support and said I would receive a call back. I have yet to receive a call but will post the results when I do.
-
Thank you Jasailafan. I tore down and rebuilt with a concentrator based on the kb article you shared and have the same anomaly. I am using same key, security, dh, etc on the tunnels and all sites have static IP. More Detail: HomeOffice 192.168.1.254 BranchA 10.0.0.1 BranchB 192.168.2.1 (unable to communicate in tunnels…
