Re: Import and export retaining open-vpn config options that are not recognized, does this exist?

[Ove Everlid <Ove Everlid sun com>]

Dan Williams wrote:
> On Fri, 2009-03-20 at 18:20 +0100, Ove Everlid wrote:
> > Hi!
> >
> > Does this support exist?
> > (the feature might be valuable for all VPN backends)
> >
> > I need some options around that NetworkManagerOpenVPN strips off when 
> > importing/exporting. Rather then adding every single item into the full 
> > GUI this will allow NetworkManager to more flexibility support "odd" 
> > setup's.
>
> I don't think this exists yet; remember that import is to allow NM to
> use the connection; it's not expected that NM will preserve unknown
> values a year or two down the road when exporting back out to a conf
> file.  If NM can't use it, what good is it sitting around in GConf?  As
> an admin, I'd expect to distribute the openvpn config file (in which
> case there's a canonical source for everyone) or the GConf XML dump that
> can be imported when the admin sets the machine up (which of course is
> NM-specific).
>
> Are you trying to use the NM dump elsewhere with a slightly different
> config?

The need arose during a time when we did not fully understand an issue 
with NetworkManager. E.g., the fact that it ignored the network mask 
passed up to OpenVPN-helper when a tun interface is used.

Now this has been fixed. The need I saw for this import is gone. I agree 
that from a maintenance point of view importing/exporting unknown fields 
will be a bit tricky.

Ove


> Dan


--
Ove Everlid
MySQL Senior Systems Architect
Mobile: +46706662363
Office: +4618174410 (Time Zone MET)
Skype handle: oveeve