[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: "Daniel L. Miller" <dmiller@xxxxxxxxx>
  • Date: Tue, 11 Sep 2007 07:46:04 -0700

Timothy Baldwin wrote:
> In message <B216E7A91F67B6429E3ACF162402A02D570C3C@xxxxxxxxxxxxxxxxxxxxx>,
> David Balazic <David.Balazic@xxxxxxxxxxxxxxxxxx> wrote:
>
>  
>   
>> The host on the remote network, like 10.4.1.150, must know where to send
>> replies. Either the VPN client (.140) masks the packet as coming from him,
>> or .150 has a route added for the source of the packets coming from your
>> VPN server. That would be 172.27.0.1, I guess.
>>  
>> So either add routes to hosts on the client LAN, or use masquerading on
>> the client. (this is actually supported by Windows : see ICS)
>>     
>
> The route added on the clients LAN needs to be to the LAN IP of the client,
> 10.4.1.140. An alternative would be add this route to the default router of
> the client's LAN.
>
> Further, if not masquerading, IP routing needs to enabled the client, see:
> http://www.windowsnetworking.com/articles_tutorials/w2kprout.html
>   
I did set the "IPEnableRouter" entry to "1" on the client.  Is that 
sufficient?
______________________
OpenVPN mailing lists
https://lists.sourceforge.net/lists/listinfo/openvpn-users