I also face the common problem with OTP support for OpenVPN that the client does not ask for a code. The server was freshly set up with core 197 and the OpenVPN-profile also was newly created.
On client-side, I have the most recent Community-client available.
No matter what I try, I’m not asked for the OTP code and the connection stalls at the same point until in times out:
I was able to solve the problem for me. Obviously still the lines making the OpenVPN-client to ask for the OTP are missing in the ovpn-files generated by IPFire.
It seems to be related to a peculiarity with windows clients where they do this if the auth-nocache option is enabled, so it has been removed in CU199 which is in testing.
I haven’t seen that in any of my update evaluations (done 7 or 8 so far).
If after pressing Enter or waiting for the minute it continued without any issues and after the reboot apache was working (you could access the WUI) then it would seem that apache had already stopped for some reason.
Would be interesting to hear if anyone else has had the problem.
I will do updates of my CU199 Testing systems as some new changes have been merged if I remember correctly.
Today I performed two tests
The first test involved pinging a remote host every 30 seconds.
The second test was without pinging. (Ping was done before turning off the tunnel, only to check the availability of the remote host).
During the first and second tests, the OTP code was entered at the beginning of the connection and did not ask for the code to be re-entered after an hour.
