Raspberry Pi VPN client setup

Business solution to host your own OpenVPN server with web management interface and bundled clients.
Post Reply
retlas
OpenVpn Newbie
Posts: 2
Joined: Sun Apr 14, 2013 8:41 pm

Raspberry Pi VPN client setup

Post by retlas » Sun Apr 14, 2013 8:44 pm

Hi Guys,

Been searching for a while.... Can't seem to find the answer.

Need to setup my Pi to connect through my OpenVPN server. Can't figure out how.

Running latest version of wheezy raspbian.

Would someone please help?

Thanks

User avatar
janjust
Forum Team
Posts: 2703
Joined: Fri Aug 20, 2010 2:57 pm
Location: Amsterdam
Contact:

Re: Raspberry Pi VPN client setup

Post by janjust » Mon Apr 15, 2013 10:53 am

a raspberry pi is "just" a linux PC running a form of Debian; do a

Code: Select all

apt-get install openvpn
to install openvpn and configure it just like a regular VPN client.

retlas
OpenVpn Newbie
Posts: 2
Joined: Sun Apr 14, 2013 8:41 pm

Re: Raspberry Pi VPN client setup

Post by retlas » Tue Apr 16, 2013 8:50 pm

Thanks, I was totally making the setup harder than it had to be. Didn't realize you could just drop the .ovpn config file into a directory.

Cheers.

User avatar
novaflash
OpenVPN Inc.
Posts: 1073
Joined: Fri Apr 13, 2012 8:43 pm

Re: Raspberry Pi VPN client setup

Post by novaflash » Thu Apr 25, 2013 11:34 am

Just throwing in my 2 cents;

If you rename the .ovpn to .conf and place it in /etc/openvpn/ the OpenVPN daemon will be able to pick it up and autostart/stop the connection on boot-up/shutdown. That does require an autologin profile, though, as the daemon will not be able to handle interactive input of username/password.
I'm still alive, just posting under the openvpn_inc alias now as part of a larger group.

denver
OpenVpn Newbie
Posts: 2
Joined: Fri May 17, 2013 6:05 pm

Re: Raspberry Pi VPN client setup

Post by denver » Fri May 17, 2013 6:07 pm

Hi,

I am trying to connect to a VPN using a raspberry Pi with Arch linux but this is what I get.... :



[root@Rpi openvpn]# openvpn AirVPN_IT-Crucis_UDP-443.ovpn
Thu Jan 1 01:57:57 1970 OpenVPN 2.3.1 armv6l-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [EPOLL] [eurephia] [MH] [IPv6] built on May 4 2013
Thu Jan 1 01:57:57 1970 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Thu Jan 1 01:57:57 1970 WARNING: file 'user.key' is group or others accessible
Thu Jan 1 01:57:57 1970 Socket Buffers: R=[163840->131072] S=[163840->131072]
Thu Jan 1 01:57:57 1970 UDPv4 link local: [undef]
Thu Jan 1 01:57:57 1970 UDPv4 link remote: [AF_INET]95.110.200.16:443
Thu Jan 1 01:57:57 1970 TLS: Initial packet from [AF_INET]95.110.200.16:443, sid=770ec53a 834ac32a
Thu Jan 1 01:57:58 1970 VERIFY ERROR: depth=1, error=certificate is not yet valid: C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
Thu Jan 1 01:57:58 1970 TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Thu Jan 1 01:57:58 1970 TLS Error: TLS object -> incoming plaintext read error
Thu Jan 1 01:57:58 1970 TLS Error: TLS handshake failed
Thu Jan 1 01:57:58 1970 SIGUSR1[soft,tls-error] received, process restarting
Thu Jan 1 01:57:58 1970 Restart pause, 2 second(s)
Thu Jan 1 01:58:00 1970 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Thu Jan 1 01:58:00 1970 WARNING: file 'user.key' is group or others accessible
Thu Jan 1 01:58:00 1970 Socket Buffers: R=[163840->131072] S=[163840->131072]
Thu Jan 1 01:58:00 1970 UDPv4 link local: [undef]
Thu Jan 1 01:58:00 1970 UDPv4 link remote: [AF_INET]95.110.200.16:443
Thu Jan 1 01:58:00 1970 TLS: Initial packet from [AF_INET]95.110.200.16:443, sid=7dbff7a1 021b283c
Thu Jan 1 01:58:00 1970 VERIFY ERROR: depth=1, error=certificate is not yet valid: C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info


Thanks for helping me out ^^

denver
OpenVpn Newbie
Posts: 2
Joined: Fri May 17, 2013 6:05 pm

Re: Raspberry Pi VPN client setup

Post by denver » Fri May 17, 2013 11:27 pm

Got the solution...

It was due to a server date and time not in synch...

Post Reply