Hi, On Fri, Nov 14, 2014 at 06:36:59PM +0200, Nikolaos Milas wrote: > Then OpenVPN v2.3.5 was built without problems. So, thanks again! > > A second question; I am currently using (in production): > > NetworkManager-openvpn-0.8.1-0.1.git20100609.el6.x86_64 > openvpn-auth-ldap-2.0.3-6.el6.x86_64 > openvpn-2.2.2-1.el6.x86_64 > pkcs11-helper-1.07-5.src.rpm > > Our config is using three server instances. Two of them are using the > net30 and one of them the subnet topology. > > Can I *simply* (i.e. as a drop-in replacement, without config changes) > upgrade by installing: > From EPEL: > NetworkManager-openvpn-0.8.1-0.2.git20100609.el6.x86_64 > easy-rsa-2.2.2-1.el6.noarch.rpm > As built by myself: > pkcs11-helper-debuginfo-1.11-1.el6.x86_64 > pkcs11-helper-1.11-1.el6.x86_64 > pkcs11-helper-devel-1.11-1.el6.x86_64 > openvpn-debuginfo-2.3.5-1.el6.x86_64.rpm > openvpn-debuginfo-2.3.5-1.el6.x86_64.rpm > ?
I'm not sure about NetworkManager (not using this myself), but the rest
should be very straigtforward - "rpm -Uvh" and off you go :-)
> Is it safe to upgrade our production installation without any changes to
> the server configuration?Are new versions backward-compatible in terms
> of configuration files/settings?
I think it should be safe. 2.2.2 to 2.3.x was not a big change in regards
to config files (functionality added, but few things actually changed).
If you have users that have CNs with blanks in them ("CN=Gert Doering")
and use CCD files, the name remapping rules have changed to accomodate
non-ASCII CNs - so the CCD files might need renaming.
At some point the location of the installed-by-default plugins changed,
but I can't remember whether that was for 2.3.x or happened inside what
will be 2.4.0 eventually. You might want to check those paths if you
use "plugin" in your config.
> Also, do the users (clients) need to upgrade immediately to the new
> version of OpenVPN (2.3.5), or they will be able to connect without
> problems with their OpenVPN versions ranging from 2.2.2 to 2.3.2?
On the protocol side, about everything is compatible with everything
else - we do our best to introduce new stuff in a way that is always
compatible. So a 2.2.2 client can talk to a git master server just
fine, and vice versa :-)
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgpgfWK4tDg4G.pgp
Description: PGP signature
------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
