Den 15. jan 2005, kl. 9:09, skrev Waleed Khan:
Here is my scenario. I have a linux vpn server with a public ip
I'm running openvpn 2.0.15-1 beta. On the client side i've got another
linux machine connected via a dsl modem to the public internet. The dsl
router is a netgear router running nat. It's private address is
192.168.0.254. I have no problem with the client linux machine talking
the vpn server. What i'm trying to do is to get the windows boxes
behind the linux machine to talk to the machines on the same network as
the vpn server. What i've done is i'm natting the tun device in
on the client linux server side. The connection from my windows boxes
using the linux client as a default gateway seems unstable. When i SSH
into machines on the same network as the vpn server it logs in , then
freezes after a type a few commands. Same with other applications ,
tend to freeze after a few seconds. I'm wondering if my set up is
Should i nat the tun device to allow my windows boxes behind the linux
client vpn machine to access the other side or is there a more reliable
way if doint this ? Here are the route commands i am using on my linux
client vpn machine.
/sbin/route add -host 184.108.40.206 (remote vpn server) gw 192.168.0.254
/sbin/route add -net 220.127.116.11(vpnserver's network address) netmask
255.255.255.0 gw 10.0.2.2 (remote vpn private ip)
you have to do the routing in both ends.
also running openvpn server 192.168.1.1
openvpn client 192.168.1.2
also gw 192.168.2.1
both GW's needs to know where to find the network for the other end.
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
Openvpn-users mailing list