[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: "David Balazic" <David.Balazic@xxxxxxxxxxxxxxxxxx>
  • Date: Tue, 18 Sep 2007 11:39:25 +0200

Title: RE: [Openvpn-users] unable to ping internal LAN after connectedtoVPN
???
 
Did you change the "push route" line ?
Did it work afterwards ?
 
David


Von: Winanjaya [mailto:winanjaya@xxxxxxxxxxxxxxxx]
Gesendet: Di 18-Sep-07 11:38
An: David Balazic; 'Eero Volotinen'
Cc: 'Klaus Thielking-Riechert'; openvpn-users@xxxxxxxxxxxxxxxxxxxxx
Betreff: RE: [Openvpn-users] unable to ping internal LAN after connectedtoVPN

I don't understand why Default Gateway was empty?


Windows IP Configuration


Ethernet adapter OpenVPN:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 10.8.0.2
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 172.16.1.27
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 172.16.1.5

PPP adapter CBN:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 202.158.107.91
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . : 202.158.107.91


pls help

TIA

Winanjaya

-----Original Message-----
From: David Balazic [mailto:David.Balazic@xxxxxxxxxxxxxxxxxx]
Sent: Tuesday, September 18, 2007 4:17 PM
To: winanjaya@xxxxxxxxxxxxxxxx; Eero Volotinen
Cc: Klaus Thielking-Riechert; openvpn-users@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [Openvpn-users] unable to ping internal LAN after
connectedtoVPN


If their default gatweay is the openvpn server, then it should work automatically.

________________________________

From: Winanjaya [mailto:winanjaya@xxxxxxxxxxxxxxxx]
Sent: Tue 18-Sep-07 11:18
To: David Balazic; 'Eero Volotinen'
Cc: 'Klaus Thielking-Riechert'; openvpn-users@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [Openvpn-users] unable to ping internal LAN after connectedtoVPN



Hi
clients on 172.16.1.0 is not OpenVPN clients.. they are Office's users..

any idea?

Regards
Winanjaya

-----Original Message-----
From: David Balazic [mailto:David.Balazic@xxxxxxxxxxxxxxxxxx]
Sent: Tuesday, September 18, 2007 4:11 PM
To: winanjaya@xxxxxxxxxxxxxxxx; Eero Volotinen
Cc: Klaus Thielking-Riechert; openvpn-users@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [Openvpn-users] unable to ping internal LAN after
connectedtoVPN


1.) push "route 172.16.1.0 255.255.255.0" instead of push "route 192.168.1. 255.255.255.0"
 
2.) what "clients" on 172.16.1.0 ? OpenVPN clients ?`
 
David

________________________________

From: openvpn-users-bounces@xxxxxxxxxxxxxxxxxxxxx on behalf of Winanjaya
Sent: Tue 18-Sep-07 11:11
To: 'Eero Volotinen'
Cc: 'Klaus Thielking-Riechert'; openvpn-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Openvpn-users] unable to ping internal LAN after connectedtoVPN




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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users