Unable to gain access to VPN on raspberry Pi

madwoollything

Hi I hope you can help.

I've been following this tutorial in turning my Pi into a VPN server http://readwrite.com/2014/04/10/raspberry-pi-vpn-tutorial-server-secure-web-browsing#awesm=~oBvYD8BOiTdCQN

I've been testing the pi out using my Nexus 7 using the OpenVPN app but am getting 'Waiting for server response'

In the /var/log/openvpn I get
Sat Oct 4 10:02:02 2014 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]149.254.219.181:46118

I'm new to this whole area but think this is suggesting a firewall setup issue on the pi so I've double checked the netgear routing settings, and the /etc/firewall-openvpn-rules.sh
#!/bin/sh
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j SNAT --to-source 192.168.0.70

And also the file ownership.

Basically I've repeated the instructions on the website several times trying to find the error in my setup with no success.
Any suggestions at to what the problem might be and how to track it down?

madwoollything

Unable to connect with raspberry pi VPN

I hope you can help.

I've followed the following guide to build a VPN server
http://readwrite.com/2014/04/10/raspberry-pi-vpn-tutorial-server-secure-web-browsing

I've set up OpenVPN on a Nexus 7 using the ca.crt, client1.crt & client1.des.key. Then using a 3G dongle to connect with the VPN server. The app reports 'waiting for server reply"

The pi /var/log/openvpn reports
Sat Oct 4 13:24:09 2014 TLS Error: cannot locate HMAC in incoming

I think that this might be a firewall issue on the pi so I've double checked all the settings including the /etc/firewall-openvpn-rules.sh

#!/bin/sh
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j SNAT --to-source 192.168.0.70

Having triple checked everything I'm stuck as what to try next. Any ideas?

Traffic

madwoollything wroteThe pi /var/log/openvpn reports
Sat Oct 4 13:24:09 2014 TLS Error: cannot locate HMAC in incoming

the problem is in your PKI.

It is best to post configs and logs of server and client.

In this case, check your --tls-auth details.