|
|
Nick Martin wrote: > Recently I had to set up a VPN for a corporate network numbered in the > 192.168/16 private range. Unfortunately, many VPN clients are also > assigned numbers in this address range. Yup, it's a problem. > After much searching for other people with this same problem, I > decided to go with the one-to-one NAT NETMAP solution proposed in > the OpenVPN FAQ. Since the directions in the FAQ weren't very clear, > and it seems many other people have had this problem, I decided to > write up a page explaining what I did. I hope other people will find > this information useful: > > http://www.nimlabs.org/~nim/dirtynat.html >From the document: >> The solution I settled on was to create a one-to-one NAT to remap all >> of corporate LAN to a different private netblock (10.22/16), and put >> the client into that range. To the hosts in the corporate network, the >> VPN client appears to be in 192.168/16 and to the client the corporate >> network seems to be 10.22/16. Not all "coffee shops" use 192.168/16. What happens when the coffee shop assigns the remote worker 10.22.0.20? Same problem. Is it solvable? -- Jamie ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2005-05/msg00006.html on line 203 Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2005-05/msg00006.html on line 203 |