Comments
-
Earlier you said to disable SNAT on the policy which I did. With the firewall still down, I re-enabled it, and now I have full traffic across the VPN, directory browsing, and pinging the photocopier. It looks like SNAT is needed for the VPN?
-
Out of interest, I tried creating an explicit rule from 192.168.50.1 to LAN1 and vice versa, the ping now no longer appears in the logs, but still doesn't get through.
-
You've taught me something (else) new. Yes it's being blocked by the default rule.
-
Hi Thanks for your help so far, but now we're getting outside of my knowledge of the Zyxel, I'm going to have to read up on logging and how it works first to answer your question, because it looks like logging is disabled by default. I'll take a look tomorrow when I'm at work and report back. Thanks
-
Just a reminder that if I turn off the firewall, everything works, so to me the issue is a firewall rule needs to be created to "allow" the traffic.
-
If you mean the Members, that was created by the Wizard. I've only used the Wizard to create the VPN settings. And yes, it's the first of 2 routes
-
Hi No, the remote PC (i.e. the one at home trying to connect via VPN) has a router 192.168.1.1 The zyxel has public IPs from 2 different providers.
-
For some reason, when I post the result of the ping, it gets blocked, but not if I post a picture of it.
-
Hi It didn't work. I still can't ping the Zyxel or anything on the LAN. I've attached the policy below.
-
Hi I'm not able to ping the Zyxel in the current config, or any IP on the LAN. I'll have a go of your suggestions above.
-
Hi Partial success. The VPN now connects, but no traffic can pass through. I'm guessing I need another rule to allow traffic to pass. I've tried the following.