GNOME Bugzilla – Bug 656214
No way to set certain config options using the nm-openvpn gui
Last modified: 2016-03-31 11:46:18 UTC
(I'm reporting a bunch of bugs that I had today with nm. NetworkManager-0.8.9997-6.git20110721.fc15.x86_64) I could find no way to set the following settings, which are recommended by openvpn for keeping a vpn connection reliable, in the gui: keepalive 10 60 ping-timer-rem persist-tun persist-key I could also not find a way to set: redirect-gateway def1 Luckily I have control over the openvpn server and can push the options, but I doubt everyone can do this too. There is a second problem that I have no idea which options nm has accepted from options pushed to the client.
The persist-tun and persist-key options are turned on by default; there is no need to set them explicitly. See bug #651657 for a semi-hacky patch to hard-code the keepalive option.
(In reply to lsof from comment #0) > (I'm reporting a bunch of bugs that I had today with nm. > NetworkManager-0.8.9997-6.git20110721.fc15.x86_64) > > I could find no way to set the following settings, which are recommended by > openvpn for keeping a vpn connection reliable, in the gui: > > keepalive 10 60 This is now supported. > ping-timer-rem Does this even make sense for client-mode? nm-openvpn can only act as client. > persist-tun > persist-key As Frederico said, those two settings are always enabled. There is currently no way to disable that (and it probably doesn't make sense). > I could also not find a way to set: > > redirect-gateway def1 With nm-openvpn, the openvpn process doesn't configure any addresses/routes itself, but tells them to NetworkManager -- which then does the configuration depending on it's configuration. This setting doesn't make sense for nm-openvpn. It's better to ask what IP configuration you want, and how nm-openvpn can be configured to achieve what you want. > Luckily I have control over the openvpn server and can push the options, but > I doubt everyone can do this too. > > There is a second problem that I have no idea which options nm has accepted > from options pushed to the client. openvpn is started by nm-openvpn with --up "/usr/libexec/nm-openvpn-service-openvpn-helper ..." argument. Openvpn will invoke this script when something changes, the script will obtain the information via environmnet variables (see "Environmental Variables" in `man openvpn`). Then it will pass part of the information on to nm-openvpn-service, which then passes it on to NetworkManager. I cannot answer your question because there are a gazillion of options and I don't know which of them make sense for nm-openvpn. It's better to ask the other way around: what do you want to do, and then let's see how to achive that. Closing this bug as fixed. Please open a new bug for any follow up issues that you still have. Thank you.