|
|
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 > > Regards, > David -- OpenPGP key fingerprint: D0A6 F403 9745 CED4 6B3B 94CC 8D74 8FC9 9F7F CFE4 ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |