OPNsense Forum

Archive => 16.1 Legacy Series => Topic started by: Ren on February 25, 2016, 08:59:43 pm

Title: [SOLVED] OpenVPN Windows Client Export
Post by: Ren on February 25, 2016, 08:59:43 pm
Hey guys, been testing opnsense for a couple days and im having an issues unpacking the Windows installer after successfully exporting the windows installer for an OpenVPN client.

No matter the exported windows installer, it always gets stuck at 0% when installing
Title: OpenVPN client won't unpack
Post by: macgvr on April 01, 2016, 10:55:18 pm
Started out setting up OpenVPN with 15.7 but I couldn't get the service to start also couldn't get the client to download. Kept getting errors I couldn't resolve. Upgraded to 16.1.8 and recreated everything. That got the service working and I was able to create a client package for windows but no matter which client version I tried, none of them would extract. Extracting just stayed at zero. I was able to get the archive and client configuration files to download and open.  I know I can manually install the client software but need to know where to put which files to get it to work right, if all of the needed files are there. That would allow me to test and see if it will meet the need.
Title: Re: OpenVPN Windows Client Export
Post by: drtubb on April 08, 2016, 09:50:58 pm
I'm having the exact same issue. Running 16.1.19 with all packages/components up to date. pfSense creates Windows .EXEs that are roughly 1.9MB, whereas the the ones OPNsense creates are roughly 132kB. Stuck at extracting 0% and appears to hang there. Must use task mgr to kill the executable. I tried reinstalling the openvpn package, to no avail.

Anyone?
 
Title: Re: OpenVPN Windows Client Export
Post by: franco on April 11, 2016, 08:09:47 am
There is little time to keep this rolling with my current day job requirements. Can somebody else look at it, at least to find out what fix is required?


Thanks,
Franco
Title: Re: OpenVPN Windows Client Export
Post by: franco on April 11, 2016, 09:55:24 am
Nevermind, will be fixed in 16.1.10. Thanks for the reports!