openvpn setup on red:
[X] openssl (0.9.8g) installed on red (pkgadd, <SMCossl>)
[X] lzo (2.0.3) library installed or red, in /usr/sfw/ (build from sources)
[ ] openvpn (2.0.9) failed (building from sources)
./configure --prefix=/usr/sfw --with-ssl-headers=/usr/local/ssl/include 
--with-ssl-lib=/usr/local/ssl/lib
gmake  (FAILED with error)

No known workaround. Bug report filed for opensolaris.

That means we cannot have openvpn running on Solaris boxes in neither server or client mode. I’ll go with PPP over SSH as planned earlier.  Or do I? OpenVPN is so much nicer to use and support. So, decided to actually check in freeBSD what the constant is, and hack/hardcode it into the tun.c  Actually, I was not the first with the idea. Patched and compiled.

<span style="line-height: 19px; white-space: normal; font-family: 'Lucida Grande';"> </span>[X] openvpn 2.1rc7 compiled and operational on red

Now we need to configure it all. But… surprise – after configuring the openvpn does not work. This time, the /dev/tun device cannot be opened.  Need to apply this patch, recompile, and try again. Remember, when executing /usr/sfw/sbin/openvpn to have your LD_LIBRARY_PATH set to /usr/local/ssl/lib:/usr/sfw/lib

Well, the saga continues. The tun-1.1 from sourceforge seems not to work on 64-bit solaris, and one needs to grab this one instead. I’m trying it now. Works.  Finally, all necessary hubs have openvpn installed and working. The alternative tun/tap driver solves issues on Solaris. Configuring DNS properly for VPN now. We are almost there.

Leave a Reply

Your email address will not be published. Required fields are marked *