If you have not defined any Static IP Address pools then you will not see the problem.
If a static address pool is defined then the problem occurs.
Correct. Thanks!
The nightly build of CU189 Testing (master branch) has completed building with the updated change for the OpenVPN issue amongst a range of changes.
I have just re-run my vm update to CU189 Testing and the add a client connection now works as expected.
To update your CU189 Testing from build 84b04cb6 to build 0555434e
You need to follow the following wiki section on Updating Testing version
https://www.ipfire.org/docs/configuration/ipfire/pakfire/testing#update-testing
EDIT:
Unfortunately not quite there yet.
The page shows now and I filled all the details out but when saving the connection it gives an Internal Server Error due to getlastip being called and that was also removed back in CU186.
EDIT2:
Fix for this has been merged and I applied the change to my vm system and a new client connection was successfully created. I installed taht client connection on my laptop and got a successful connection which I could ping in both directions.
The nightly build for that should be completed tomorrow and I will test a re-update of the CU189 Testing to finally confirm.
3 Likes
Build a7ac62f4 has the fix for OpenVPN. I have done a core update again with my system and confirmed that the fix is in place.
Creating a new client connection worked without any issues.
Tested the new client connection with my laptop and was able to successfully make a connection. Old client connection also still functioned.
So this issue with OpenVPN looks to have been fixed.
Please can some other users re-do the Core Update 189 Testing update, as per my link in my previous post, to confirm that this now fixes the issue that was identified.
4 Likes
I confirm, with build a7ac62f4 I created a new connection with static ip and it works fine.
I tried the connection with new client and it works fine
1 Like