----- Original Message ----- > ----- Original Message ----- > > On Thu, Jan 12, 2012 at 1:00 PM, Tim Nelson <[email protected]> > > wrote: > > > Greetings- > > > > > > I understand the functionality of the OpenVPN Status package from > > > the 1.x versions is now integrated into the 2.x versions. > > > *However*, > > > let's say... "hypothetically" a 1.2.2 config was uploaded to a > > > fresh > > > 2.0.1 installation, and the OpenVPN Status package XML(every > > > package > > > XML for that matter) wasn't removed from that config as directed > > > in > > > the upgrade guide. During the package installation/setup after the > > > first boot on the imported config, it appears the system > > > downloaded > > > and installed the OpenVPN Status package, even though 2.0.1 has > > > this > > > functionality already. Now, none of the OpenVPN Status functions > > > work, citing no management daemon connection, etc. > > > > > > > The package doesn't reinstall on upgrade, as it isn't there. Don't > > think that's related to the package being there. What you're > > probably > > seeing is the custom options you have defined in your OpenVPN > > instances have to be removed so the auto-added ones work. > > I distinctly remember seeing it 'reinstall' that package on the first > boot. And, from the 'Status' menu, I have *two* entries for 'OpenVPN' > which further leads me to believe both the integrated *and* package > versions are present. > > I'll recheck the config options to see if that makes a difference. >
Well, I removed the manual management options from the VPN configs and all is working well. However, I still do have the duplicate 'OpenVPN' entries under the 'Status' menu. Not an issue, just an oddity. Thanks for the pointers Chris! --Tim _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
