[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

Re: [Openvpn-users] unable to ping internal LAN after connectedtoVPN


  • Subject: Re: [Openvpn-users] unable to ping internal LAN after connectedtoVPN
  • From: Eero Volotinen <eero.volotinen@xxxxxxxxxxx>
  • Date: Tue, 18 Sep 2007 12:51:27 +0300

Winanjaya kirjoitti:
> Hi mine was:
> 
> 192.168.1.0/24 --> client --> openvpn (10.8.0.1) --> 172.16.1.0/24
> 
> I want clients on 192.168.1.0/24 should be able to reach 172.16.1.0/24
> and all clients on 172.16.1.0/24 should be able to reach 192.168.1.0/24

Use push route 172.16.1.0 255.255.255.0 on serverside (openvpn) and use 
routing table to define route to 192.168.1.0/24 via 10.8.0.1 on office 
clients (usually you can define static route on your firewall to do this 
or dhcp? )

for example on office linux machine you need something like that:
route add -net 192.168.1.0/24 gw ip.address of openvpn-server in windows 
it is almost similar, only syntax differs.

Mainly your need to tell on both ends only correct routing table.
Windows client's don't need where they can find route to 192.168.1.0/24.

If your openvpn box is firewall/default gw, then this is easy.'



______________________
OpenVPN mailing lists
https://lists.sourceforge.net/lists/listinfo/openvpn-users