HEADS UP: Updated OpenVPN Client Export package 1.2.5 for Heartbleed fix

[pdrass]

I saw your same answer on another post and I just can't believe that.  So, what I did was MANUALLY make the calls and this is where I'm at - the packages are fetched.  I suspect it's having a difficult time actually extracting the packages where they go.

---

[2.1.2-RELEASE][root@pfs1.somedomain.local]/root(5): mount -o rw /dev/ufs/pfsense0

[2.1.2-RELEASE][root@pfs1.somedomain.local]/root(7): cd tmp

[2.1.2-RELEASE][root@pfs1.somedomain.local]/root/tmp(8): ls
apkg_iperf-2.0.5-i386.pbi  apkg_zip-3.0-i386.pbi
apkg_p7zip-9.20.1-i386.pbi

[2.1.2-RELEASE][root@pfs1.somedomain.local]/root/tmp(9): fetch https://files.pfsense.org/packages/openvpn-client-export/openvpn-client-export.tgz
openvpn-client-export.tgz                    100% of 3778 kB  438 kBps

[2.1.2-RELEASE][root@pfs1.somedomain.local]/root/tmp(10): ls
apkg_iperf-2.0.5-i386.pbi  apkg_zip-3.0-i386.pbi
apkg_p7zip-9.20.1-i386.pbi openvpn-client-export.tgz

---

So, now that we've established no proxies or antivirus scanners upstream are blocking anything what now?

Can I install it manually?

• By the way, I'm on the embedded 32 bit version on an ALIX board with 3 ports wan,lan, opt.  Not sure it matters BUT I saw a post that one user posted saying not all packages on the web ui can be installed on embedded boxes:

https://forum.pfsense.org/index.php?topic=12995.0

Is that possibly my problem?  Do I need to trick the system into thinking it's not the embedded version then flip it back after the install?

• Note:  32 bit ALIX board install here
  ** Note:  I imported the config from a PC, I'm going to setup a brand new ALIX, same everything but a fresh install, re-setup manually with NO import.  I think the import dirtied up the config even though other packages like iperf seem to install, openvpn-export-utility doesn't seem to be installing, probably because it does more complex things than iperf eh?

I'll update the post with my results.

[robi]

@pdrass:

• By the way, I'm on the embedded 32 bit version on an ALIX board with 3 ports wan,lan, opt.  Not sure it matters BUT I saw a post that one user posted saying not all packages on the web ui can be installed on embedded boxes:

https://forum.pfsense.org/index.php?topic=12995.0

Is that possibly my problem?  Do I need to trick the system into thinking it's not the embedded version then flip it back after the install?

Can't  be. The OpenVPN Client Export package installs perfectly on NanoBSD boxes. I have several of them.
Do you have enough free disk space?

[phil.davis]

• By the way, I'm on the embedded 32 bit version on an ALIX board with 3 ports wan,lan, opt.  Not sure it matters BUT I saw a post that one user posted saying not all packages on the web ui can be installed on embedded boxes:

https://forum.pfsense.org/index.php?topic=12995.0

Is that possibly my problem?  Do I need to trick the system into thinking it's not the embedded version then flip it back after the install?

OpenVPN Client Export Utility is a properly supported package on nanoBSD "embedded". There should be no need to trick the system into anything here. In fact, the available packages list on nanoBSD webGUI already has the unsupported packages filtered out.

Sorry, I have no clue what is the cause of your problem - I have installed this package on at least 4 32 bit Alix system running 2.1.2 with no trouble.

[jimp]

Is the file correct?

SHA256 (openvpn-client-export.tgz) = 288fe93bf33c596019b1dddf5400e49a8018457328ad0530df3a2a924a52fda1

If so, then it may be a disk space issue or similar. I have yet to see it fail on any other installation.

[pdrass]

FYI - my problem was fixed by doing a clean install.  I would think the backup and restore function in PFSense would be hardware agnostic but there must be something in there that's hardware specific thus taking the settings from a full intel pc to an alix board something was lost in translation.  Whatever it was broke the package installation for openvpn.

Weird, good thing I had a spare system on me ;-)

[breusshe]

@jimp:

If you're on amd64:

fetch https://files.pfsense.org/packages/8/All/p7zip-9.20.1-amd64.pbi
rm -rf /var/db/pbi/installed/p7zip-9.20.1-amd64/
pbi_add -f --no-checksig p7zip-9.20.1-amd64.pbi

Need to update the amd64 instructions because the fetch path was not correct:

fetch https://files.pfsense.org/packages/amd64/8/All/p7zip-9.20.1-amd64.pbi
rm -rf /var/db/pbi/installed/p7zip-9.20.1-amd64/
pbi_add -f --no-checksig p7zip-9.20.1-amd64.pbi

I've used the above steps on my amd64 setup and they work once the URL path in the fetch command is corrected.

–
Brett Ussher

[jimp]

Thanks. I fixed my earlier post.

The URLs were right on the doc wiki though:
https://doc.pfsense.org/index.php/Pbi_add:_Invalid_file_for_usercheck

[Jamerson]

I've updated my current version, now it shows 1.2.8 !
but the post is about 1.2.5 is between the time been a new release?

thank you

[jimp]

It's actually 1.2.9 now. Any version 1.2.5 or later is fine for this issue.

[Jamerson]

@jimp:

It's actually 1.2.9 now. Any version 1.2.5 or later is fine for this issue.

I've noticed this too :) updated and all is working great
you guys are the best