Use the Driver Verifier GUI to exclude covpnv64.sys during its processing. Perform your driver debug and test on a VM image running Driver Verifier while the host machine, where Driver Verifier is not running, connects to the corporate VPN. If you are developing a driver and your corporate environment requires BIG-IP Edge Client or its web browser components for VPN connections, you can do either of the following: Do not use BIG-IP Edge Client or its web browser components to attempt to establish a VPN connection if you plan to run Windows Driver Verifier. Do not execute Windows Driver Verifier when running BIG-IP Edge Client or its web browser components if you plan to establish a VPN session.
You can prevent this issue from occurring using either of the following suggestions:
You try to establish a VPN connection using BIG-IP Edge Client software or a web browser. Windows Driver Verifier is running on your Microsoft Windows-based device.
If your company requires F5-based VPN connections when working from a remote environment, this issue prevents you from debugging and testing Windows drivers during development without additional considerations, as described in the Workaround section. You must reboot the Windows device to restore functionality. This occurs because Driver Verifier detects an error condition in a Windows driver, in this case the F5 VPN driver covpnv64.sys, which occurs whenever you initiate an F5-based VPN connection. How would I need to configure the access policy for this to work? I tried with and without a logon page, but I don't seem to be getting a username and/or password passed through from the client, none of the session variables show the values from the edge client config file.When Windows Driver Verifier is running on the Windows-based device, and you try to establish a VPN connection using BIG-IP Edge Client components, interaction with the VPN driver covpnv64.sys results in a Windows stop error/hard crash. I guess I would need to set the connectivity profile to allow password caching and save it to disk, but can I make that change, download the package with those options, and then change it back as we generally don't want the passwords to be cached?
Even if I edit the file and save it, it just ignores the password I put in there and removes it afterwards. I went back and checked my F5 settings, and sure enough the save password on exit setting is set to false. I keep getting authentication failures, and when I check the client.f5c, I see that it has not saved my password. This needs to be done in the background as it is using straight username and password authentication and we don't want the users to see that. To briefly summarize, this is for a remote password self-service application, so I need for the client machines to be able to do a remote command line access using "f5fpc -start /c "C:\Program Files\F5 VPN\client.f5c /t /q" so the users don't get any prompts or pop-ups, the client.f5c file has to provide the username and password and server to connect to, then the password self service app does its thing, and finally issues the command "f5fpc -stop" at the end to close the VPN session out.
I am trying to get our F5 11.4 APM set up to work with remote Windows clients that need to connect and then disconnect from the VPN without any user interaction.