I apologize for the late response, this project was abandoned by the client.
Main Topics
Browse All TopicsI have been trying to setup a routed vpn tunnel between two sites on a pair of WRT54GL's to replace the OpenVPN software implementation previously in place.
10.0.0.0 is the host network, 192.168.0.0 is the client network, 172.16.8.0 is the tunnel's subnet. The client connects and the entire client network can access the host network, however when I attempt to ping 192.168.0.1 (the client router) from the host router (using ssh) it times out. I can ping 172.16.8.6 (it's address on the tunnel subnet). The old software implementation did not have this problem.
In short:
Host --> Client : Fails
Client --> Host : Works
I've been fighting this thing for nearly two days now, any help would be appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: RedimidoPosted on 2008-10-24 at 22:57:05ID: 22801841
First, I would say your firewall can be simpler:
tml#scope
---------- ---------- ---------- ----------
---------- ---------- ---------- ----------
iptables -I INPUT 1 -p udp --dport 1195 -j ACCEPT
iptables -I FORWARD 1 -j ACCEPT
iptables -I FORWARD 1 -i tun+ -j ACCEPT
iptables -I FORWARD -i br0 -o tun+ -j ACCEPT
iptables -I FORWARD 1 -s 192.168.0.0/24 -o tun+ -j ACCEPT
### Why masquerading? iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o tun0 -j MASQUERADE
Next, you need the server lan to access the client lan. this is pretty well explained in the OpenVPN howto:
http://openvpn.net/howto.h
scroll for the entry: "Including multiple machines on the client side when using a routed VPN (dev tun)"
This is an extract.. in the site it is more clear I guess:
--------------------------
this is basically add in the server.conf file
client-config-dir ccd
The next step is to create a file called client2 in the ccd directory. This file should contain the line:
iroute 192.168.0.0 255.255.255.0
Next, add the following line to the main server config file (not the ccd/client2 file):
route 192.168.0.0 255.255.255.0
Why the redundant route and iroute statements, you might ask? The reason is that route controls the routing from the kernel to the OpenVPN server (via the TUN interface) while iroute controls the routing from the OpenVPN server to the remote clients. Both are necessary.
Next, ask yourself if you would like to allow network traffic between client2's subnet (192.168.4.0/24) and other clients of the OpenVPN server. If so, add the following to the server config file.
client-to-client
push "route 192.168.4.0 255.255.255.0"
This will cause the OpenVPN server to advertise client2's subnet to other connecting clients.
The last step, and one that is often forgotten, is to add a route to the server's LAN gateway which directs 192.168.0.0/24 to the OpenVPN server box (you won't need this if the OpenVPN server box is the gateway for the server LAN).
--------------------------
hope this help