Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I recently installed OpenVPN on my Ubuntu VPS. Whenenver I try to connect to it, I can establish a connection just fine.

However, everything I try to connect to times out.

If I try to ping something, it will resolve the IP, but will time out after resolving the IP. (So DNS Server seems to be working correctly)

My server.conf has this relevant information (At least I think it's relevant. I'm not sure if you need more or not)

port 1194
proto udp
dev tun
ca ca.crt
cert server.crt
key server.key  # This file should be kept secret
dh dh1024.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "redirect-gateway def1 bypass-dhcp"
push "dhcp-option DNS 8.8.8.8"
;push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"
;client-to-client
;duplicate-cn
keepalive 10 120
;tls-auth ta.key 0 # This file is secret
comp-lzo
persist-key
persist-tun
status openvpn-status.log
# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

I've tried on multiple computers by the way. The same result on all of them.

What could be wrong?

Thanks in advance, and if you need other information I'll gladly post it.

Information for new comments

root@vps:~# iptables -L -n -v
Chain INPUT (policy ACCEPT 862K packets, 51M bytes)
 pkts bytes target     prot opt in     out     source               destination 

Chain FORWARD (policy ACCEPT 3 packets, 382 bytes)
 pkts bytes target     prot opt in     out     source               destination 
    0     0 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
 4641  298K ACCEPT     all  --  *      *       10.8.0.0/24          0.0.0.0/0   
    0     0 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           reject-with icmp-port-unreachable

Chain OUTPUT (policy ACCEPT 1671K packets, 2378M bytes)
 pkts bytes target     prot opt in     out     source               destination 

And

root@vps:~# iptables -t nat -L -n -v
Chain PREROUTING (policy ACCEPT 17937 packets, 2013K bytes)
 pkts bytes target     prot opt in     out     source               destination 

Chain POSTROUTING (policy ACCEPT 8975 packets, 562K bytes)
 pkts bytes target     prot opt in     out     source               destination 
 1579  103K SNAT       all  --  *      *       10.8.0.0/24          0.0.0.0/0           to:SERVERIP

Chain OUTPUT (policy ACCEPT 8972 packets, 562K bytes)
 pkts bytes target     prot opt in     out     source               destination 
share|improve this question
    
Can you please paste the complete server.conf here. –  GeekRide Dec 13 '12 at 7:05
    
@GeekRide Full server.conf posted, thanks! –  Austin Dec 13 '12 at 7:12
    
Could you check that the routing is activated on your server ? Is the NAT correctely configured ? If there is no nat, could you check your back route too ? –  Dom Dec 13 '12 at 7:49
1  
My suspicion is the NAT, too; could we see the outputs of iptables -L -n -v and iptables -t nat -L -n -v? –  MadHatter Dec 13 '12 at 7:51
    
@MadHatter I posted the outputs of what I think it is you want. –  Austin Dec 13 '12 at 7:54
show 8 more comments

1 Answer 1

So, what you are missing in your conf is - Routing.

The entry like this:

;push "route 192.168.10.0 255.255.255.0"

is commented into your config file. That explains why you are getting the IP but not able to ping, as there is no route information in your config file.

Uncomment this line and replace the IP information with the IP of your gateway where you are running the openvpn server.

Once you do that, your problem should be fixed.

share|improve this answer
    
How exactly would I find this? Is it just a matter of doing an ifconfig? Thanks –  Austin Dec 13 '12 at 7:55
    
Yes, on your gateway. –  GeekRide Dec 13 '12 at 8:00
    
It doesn't seem to be working for me, still getting timeout errors. –  Austin Dec 13 '12 at 8:04
    
That's bad. Let me see if there could be anything else. –  GeekRide Dec 13 '12 at 8:14
2  
just fyi ... Please send the route table after connecting to the VPN. That way we could be sure that where exactly the issue is, Server or Client. –  GeekRide Dec 15 '12 at 7:09
show 5 more comments

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.