[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: "Winanjaya" <winanjaya@xxxxxxxxxxxxxxxx>
  • Date: Tue, 18 Sep 2007 15:55:01 +0700
  • Importance: Normal

Hi.. 
it seems like OpenVPN override all routes..

My topology is :

192.168.1.0/24 --> client --> openvpn 

Any idea?

Thanks

Winanjaya



-----Original Message-----
From: Eero Volotinen [mailto:eero.volotinen@xxxxxxxxxxx]
Sent: Tuesday, September 18, 2007 3:47 PM
To: winanjaya@xxxxxxxxxxxxxxxx
Cc: 'Klaus Thielking-Riechert'; openvpn-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Openvpn-users] unable to ping internal LAN after
connectedtoVPN



Winanjaya kirjoitti:
> Sorry, I don't understand what you mean.. could you please more detail?
> 
>> push "route 192.168.1. 255.255.255.0" ==>  I thought this command should
> define route to 192.168.1.0/24 at client side
> 
> pls correct me If I'm wrong

It means route all traffic to 192.168.1.0/24 via openvpn server.

So, your topology looks like that:


client->openvpn-> 192.168.1.0/24 ip addresses.

--
Eero

***********************
Your mail has been scanned by MSS.
***********-***********



***********************
No virus was detected in the attachment (no filename).

Your mail has been scanned by InterScan.
***********-***********

____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users