[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 16:11:38 +0700
  • Importance: Normal

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

pls advise

Regards
Winanjaya

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



Winanjaya kirjoitti:
> Hi..
> it seems like OpenVPN override all routes..
>
> My topology is :
>
> 192.168.1.0/24 --> client --> openvpn
>
> Any idea?

So, remove that push route statement from openvpn server configuration.

Also if there is subnet behind openvpn server, it *cannot* overlap the
lan subnet/ip range.

For example:


192.168.1.0/24 --> client --> openvpn -> 192.168.0.0/24 is correct solution.

--
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