I turned it on in the firewall, and it started working. It turned out to be a problem with Perfect Forward Secrecy - the firewall didn't select it by default, and the VPN client did. When I got through everything, the tunnel wouldn't start. The second rule he added was the one you described. Instead of the L2TP-VPN rule, he added a rule from IPSec_VPN to ZyWALL, source any, dest any, service any, allow. The tech claimed that he'd never heard of a service called L2TP-VPN, but maybe he just wanted to get me off of the phone. I called ZyXEL support, and the tech logged into my firewall and added the two necessary rules.

That service doesn't exist on my firewall. Firewall rule featuring the L2TP-VPN service. I hit a few snags in your instructions that I was able to work through. have LMI into that client anyway so don't need the vpn.Īlso reading through this now: SSL VPN Setup ZyXel SSL VPN $75 for 10 annually after that - pretty cost effective.īut I definitely was wondering about zyxel's ipsec vpn and sslvpn - just looked at one today and was confused by its implementation and just started working on something else. Spin up a openvpnAS box and link it to your AD. Hopefully the differences will be minimal (if any) once you've updated to the latest firmware. Unfortunately, there are differences between the different USG devices in terms of the specifics required for a working VPN setup. Make sure the firmware is up to date on your Zyxel. I like David_CSG's writeup - going to test that on a USG 50 right now.

LOL those old links could also be the problem in your area!

Zywall ipsec vpn client mac os 10.14