Bug #9169
closed
carriage return handling in OpenVPN custom Options
0%
Description
For one of my OpenVPN server, I use the custom options field to push routes to my client. Eg, I add
push "route 10.29.0.0 255.255.0.0"
push "route 192.168.20.0 255.255.255.0"
push "route 192.168.23.0 255.255.255.0"
Problem is, after saving, everything is fine, but if I edit the OpenVPN Server again, carriage returns in this fields are gone, everything is on a single line
push "route 10.29.0.0 255.255.0.0"push "route 192.168.20.0 255.255.255.0"push "route 192.168.23.0 255.255.255.0"
And if I save again, OpenVPN will fail. Same after a reboot, OpenVPN will fail to start. I have to go in edit the custom options field to add the carriage return back, and save
Updated by Chris Linstruth over 5 years ago
- Status changed from New to Rejected
Separate your custom options with a semicolon as the field instructions and documentation state.
Enter any additional options to add to the OpenVPN server configuration here, separated by semicolon.
Updated by Daniel Berteaud over 5 years ago
Ok, my bad. But this is counter intuitive as the field itself is multi-line capable, and OpenVPN syntaxe doesn't need any ;