TriLanSupport  Freshman Member

Have updated to this release and we look to be seeing a possible memory leak or high memory usage that results in SSL VPN connections randomly dropping. Only resolution is to then reboot firewall and usage returns to approx. 50% Has anyone else experienced issues with high memory usage and/or leaks?

@smb_corp_user, I'm referring to the main Zyxel Download library - not articles that are posted and are therefore not current. Go here and you'll find that the Windows SSL VPN client is no longer there. I'm well aware you can download the original 4.0.4.0 version elsewhere, but I'm looking to understand why it's gone from…

As in replaced with a subscription based version?

Yes I do still have references to the created AD service - however the references search provides no details suggesting there are no references. I will continue to look but perhaps could you provide some guidance on where to check for any hidden references?

Thanks @Zyxel_Andrew for the update. In my case for those that have upgraded I've provided the L2TP workaround and for those that haven't I told them to wait until we let them know an updated package is available and tested.

Does @Zyxel_Support monitor these threads? It would be helpful to have a comment or acknowledgement on this.

Thanks for the response @Zyxel_Jeff, next time I get an occurrence report I'll runs these checks. I know from the previous occurrences that likely the ping traffic is being blocked or gets lost on the way back as the inbound count increases while outbound does not - so this would point to an outbound policy or it's…

Thanks for the steps and link. Will try this process when I get in front of device and update.

It just returns an error in the log saying it "cannot contact the server", which is the destination WAN IP of the firewall. I confirmed that the client could by other means, so don't have much more to go on. It worked before the update and now it doesn't. I have asked the customer to update to 13.2.1 to see if this…

I should clarify, the affected Mac was running the latest version available and was working OK. After the user updated to Ventura, it stopped working. I have already removed/reinstalled the client and the problem persists under Ventura 13.2.