Using the latest version of ZA (free ver.) in conjunction with OpenVPN (VPN client), I have noticed that the "adapter subnet" for for my "VPN" network adapter (virtual, created by OpenVPN) will not be updated correctly by ZA.
During the process of establishing a VPN tunnel, OpenVPN will use DHCP (and/or other methods) to assign the correct (localnet) IP to the adaptor (as indicated by the VPN server at the other end of the tunnel). When doing so, ZA seem to stay "locked" on whatever arbitrary IP the adaptor was assigned by DHCP before (or during) the VPN tunnel was connected. Thus, when the VPN tunnel is established, ZA will block everything as it doesn't "trust" the (correct) adapter subnet, forcing me to shutdown and restart ZA for things to start working properly (ie. to see the right adapter subnet in ZA's list of trusted subnets, and thus get traffic through the VPN tunnel).
I assume the problem is that ZA doesn't "realise" that the adaptor subnet is being changed during the VPN connection sequence (possibly due to some non-standard method being used), and hope you will look into this problem and possibly have it fixed in furture versions..?
Thanks a lot,
P.S. FYI: According to the OpenVPN log/status it is using "IPAPI" to change the adapter IP/subnet, if that helps any?
Operating System:Windows 2000 Pro
Product Name:ZoneAlarm (Free)