Feature #7621
closedOpenVPN Client Export name whens is a windows installer have the same name its a bit confused
0%
Description
When you export a OpenVpn files it's not possible distinguished by the name file between win6, x86, x64, xp, etc.
For example, if you downloaded the 4(four) types you will have on /home/<user>/Downloads:
pfSense-udp-1194-prolinx-install (1).exe
pfSense-udp-1194-prolinx-install (2).exe
pfSense-udp-1194-prolinx-install (3).exe
pfSense-udp-1194-prolinx-install (4).exe
So, it's a bit confused to check which one is win6-x64 in this case. My suggestion is improve the name just for windows with pfSense-<protol>-<port>-<user>-<plataform-osversion>-install.exe.
So, will be liek that for Windows 10, 64 bits: pfSense-udp-1194-prolinx--x86-win6-install.exe
You can improve that, just changing the line 328 (master) on vpn_openvpn_export.php:
before:
$exp_name = urlencode($exp_name."-install.exe");
after:
$exp_name = urlencode($exp_name."-".substr($act, 5)."-install.exe");
Updated by André Araujo over 8 years ago
Fixing the sentence:
So, will be like that for Windows Vista, 64 bits: pfSense-udp-1194-prolinx-x64-win6-install.exe
Updated by robi robi over 8 years ago
+1 for this. We're exporting both x86 and x64 versions for each user, because we don't see in advance which os version they use.
Updated by Jim Pingle over 8 years ago
- Status changed from New to Feedback
- Assignee set to Jim Pingle
I pushed a change to add more detail to the filename, but I used a different tactic so it will be more accurate.
That said, unless you have a user with Windows XP, you should always be using the OpenVPN 2.4 installer no matter what (it does both 32 and 64-bit). There is no reason to keep using the OpenVPN 2.3.x installer unless you have a rare edge case where the client doesn't work properly with 2.4. I've not seen one of those yet, the 2.3.x installers are mostly around for XP or just in case.