So to make it short i followed this guide to install OpenVPN SERVER.....
http://melgrubb.wordpress.com/2014/08/0 ... openvpn-2/
but it fails to start when i issue /etc/init.d/openvpn start
"[FAIL] Starting virtual private network daemon: server failed!"
/var/log/openvpn.log and /var/log/openvpn-status.log are both EMPTY
my conf:
local 192.168.0.3 # YOUR PI▒^▒^▒S IP ADDRESS
dev tun
proto udp
port 1194
ca /etc/openvpn/easy-rsa/keys/ca.crt
cert /etc/openvpn/easy-rsa/keys/closet_server.crt
key /etc/openvpn/easy-rsa/keys/closet_server.key
dh /etc/openvpn/easy-rsa/keys/dh1024.pem
server 10.8.0.0 255.255.255.0
# server and remote endpoints
ifconfig 10.8.0.1 10.8.0.2
# Add route to Client routing table for the OpenVPN Server
push "route 10.8.0.1 255.255.255.255"
# Add route to Client routing table for the OpenVPN Subnet
push "route 10.8.0.0 255.255.255.0"
# your local subnet
push "route 192.168.0.3 255.255.255.0" # YOUR PI▒^▒^▒S IP ADDRESS
# Set primary domain name server address to the SOHO Router
# If your router does not do DNS, you can use Google DNS 8.8.8.8
push "dhcp-option DNS 192.168.0.1" # YOUR ROUTER▒^▒^▒S IP ADDRESS
# Override the Client default gateway by using 0.0.0.0/1 and
# 128.0.0.0/1 rather than 0.0.0.0/0. This has the benefit of
# overriding but not wiping out the original default gateway.
push "redirect-gateway def1"
client-to-client
duplicate-cn
keepalive 10 120
tls-auth /etc/openvpn/easy-rsa/keys/ta.key 0
cipher AES-128-CBC
comp-lzo
user nobody
group nogroup
persist-key
persist-tun
status /var/log/openvpn-status.log 20
log /var/log/openvpn.log
verb 1
i have googled the net far and near and most of them shows that the tun network interface is up, but that is not the case for me. and only one hit came close, that one was due to 2 conf file in same dir but i have only one.
also most guides say reboot and config firewall... i dont have a firewall as that is in my router... and i cant reboot since its a server other people is also depending on, to make it worse the pi is also doing energy loging and rebooting will make a mess in the data as it will use year 1970 until it gets a valid date from the internet... enough to screw up the data
but where can i start to look for faults?
zgrep CONFIG_TUN /proc/config.gz
CONFIG_TUN=m