Bug #11015
closed
Unable to use double quotes in openvpn custom options
Added by Todor K over 3 years ago.
Updated over 3 years ago.
Affected Version:
2.4.5-p1
Description
If double quotes are used in openvpn custom options field, the service breaks and does not start.
Example:
Adding similar line somewhere before the last line
push "socket-flags TCP_NODELAY"
then Save, will make the next line join this one which breaks the configuration and openvpn service does not start.
There are two workarounds:
1. Use single quotes.
2. If you have only one line with double qotes, make it the last line in "custom options".
- Status changed from New to Rejected
Did you separate lines with semicolons as instructed?
This should probably be taken to the forum to determine if this is really a bug or just a failure to follow instructions.
Rejecting because this tests fine:
reneg-sec 43200;
route 172.25.64.128 255.255.255.128;
push "inactive 3600 32768";
push "route 172.25.232.0 255.255.255.0";
push "socket-flags TCP_NODELAY";
push "route 172.25.228.0 255.255.255.0"
Resulting ovpns1.conf:
reneg-sec 43200
route 172.25.64.128 255.255.255.128
push "inactive 3600 32768"
push "route 172.25.232.0 255.255.255.0"
push "socket-flags TCP_NODELAY"
push "route 172.25.228.0 255.255.255.0"
Well, yes you are right. But it's confusing as openvpn's config file format has no semicolons, the example also has no semicolons, and at the end - it works fine if the options are listed one per line.
But in any case I don't think modifying the user input is correct behavior - what I have initially described. Typing wrong configuration options is one thing, changing what I've typed (and joining lines) is a bit different.
Anyway. Thanks!
Also available in: Atom
PDF
Updated by 
Updated by