Importing an OpenVPN config file does not fill all supported options

Milan,

When you import the configuration file, are your certificates also in the same path as the imported file?

I'm confirming this bug, as I can currently notice that behaviour in Karmic with the attached configuration file: certificates are missing (which is probably normal since I don't have them), and the port specified in the config as well.

The connection port doesn't appear to ever be imported from the config as per even the latest git snapshot available, so I'll mark this as importance: Wishlist, since it requires implementing some new stuff.

Currently supported parameters appear to be only the following: "client", "tls-client", "dev ", "proto ", "remote ", "ca", "cert", "key", "cipher", "comp-lzo", "ifconfig ", "secret", "auth-user-pass", "tls-auth", "auth ", "reneg-sec".

Reported as gnome bug 604329 for importing/exporting already supported options.

It appears that there also was gnome bug 484315 for other options I found in your config file: mtu, etc.

Yeah, the certificate was also in the same dir. That can hardly affect importing of settings, though.

I don't think bgo#484315 is really related since I'm able to connect to my VPN when I enter the settings manually into nm-connection-editor.

(And, sorry, I could have reported it upstream myself - I reported it in Ubuntu first because I wanted to be sure that wasn't known to be fixed in a newer version, and then I forgot about the report.)

Milan,

The certificate needs to be in the same directory for NM to use it's current logic (default path... unless I missed something) to take a guess as to its location since it's not specified in your configuration file.

I linked bgo #484315 since it mentions tun-mtu and mssfix which are included in your config file, but for which I could not find import logic at first glance.

With a little luck I should be able to tackle this issue and provide a draft patch that ensures 'port' and any other options already provided by the UI are properly imported, so I'll assign this to myself for now.

This bug was fixed in the package network-manager-openvpn - 0.8-0ubuntu1

---------------
network-manager-openvpn (0.8-0ubuntu1) lucid; urgency=low

  * upstream release 0.8
    - core: add tls-remote support (bgo #455142)
    - export: fix tls-auth export
    - import/export: handle 'port' and 'rport' correctly (bgo #604329) (LP: #443174)
    - build: disable .desktop file for now
    - core: handle remote VPN peer correctly in shared key mode too (bgo #606998)
  * bump build-depends to >= 0.8 to build with 0.8 final.
    - update debian/control
  * don't install nm-openvpn.desktop, it's not being built
    - update debian/network-manager-openvpn.install
  * don't install the associated mime-type icon either
    - update debian/network-manager-openvpn-gnome.install
 -- Mathieu Trudel <email address hidden> Fri, 19 Feb 2010 08:58:49 -0500

does network-manager-vpn support route for import function?
It seems that route could not be imported into network-manager-vpn