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

Re: [Openvpn-users] Access to client-side subnet via routed VPN


  • Subject: Re: [Openvpn-users] Access to client-side subnet via routed VPN
  • From: Luke Kearney <lkearney@xxxxxxxxxxxxx>
  • Date: Tue, 11 Sep 2007 23:40:56 +0900

Daniel L. Miller wrote:
> Luke Kearney wrote:
>   
>>>> The VPN uses the 172.27.0.0/16 network.  The VPN server, on tun0, is 
>>>> 172.27.0.1.  The VPN client is 172.27.0.14.
>>>> The VPN server exists on its LAN 192.168.0.0/24 as 192.168.0.71.
>>>> The remote client has a remote LAN address of 10.4.1.140.  I'm trying to 
>>>> reach 10.4.1.150 through the VPN.
>>>>       
>>>>         
>>> Ok, you need to tell the VPN server that the subnet 10.4.1.140/?? exists
>>> at this point in time you appear to have a Client Server VPN tunnel
>>> established but no site to site. Assuming your remote network is
>>> 10.4.1.0/24 add something like this to your server configuration
>>>
>>> route 10.4.1.0 255.255.255.0
>>>
>>> And restart - Failing any firewalling done on your remote client at
>>> 10.4.1.140 you should now be able to ping hosts on that subnet via the
>>> VPN tunnel.
>>>     
>>>       
> I currently have:
>
> route 10.4.1.0 255.255.255.0
>
> in my sever configuration and
>
> iroute 10.4.1.0 255.255.255.0
>
> in the ccd/client file.
>
> I am still unable to ping other hosts on the remote network.
>   

Just a guess but do the remote hosts have routing information for this
new VPN network? Had IP forwarding/Routing been turned on in the client
at 10.4.1.140?
______________________
OpenVPN mailing lists
https://lists.sourceforge.net/lists/listinfo/openvpn-users