<p dir="ltr">If this is for home use, then you probably have only 1 public IP and are using NAT internally. If so, you can publicly host DNS that exposes your private IPs (10. or 192.168. etc.) with impunity. </p>
<div class="gmail_quote">On Nov 13, 2012 5:04 PM, "Brian MacLeod" <<a href="mailto:nym.bnm@gmail.com">nym.bnm@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
On 11/13/12 4:50 PM, Robert L. Harris wrote:<br>
><br>
> yeah, didn't think it was possible, would be nice though.<br>
><br>
<br>
On the other hand, should you have your own domain, you could publish<br>
(*PUBLICALLY*) addresses to your internal network (or use external<br>
addresses), and then specifically tell OpenVPN to push routes that<br>
would direct traffic to those destination IPs through the VPN<br>
connection. If you publish the externals, redirecting gets messy --<br>
you also have to get a little loose with any firewall/forwarding rules<br>
on the VPN hosts (and potentially intervening hosts, since they need<br>
to know how to route packets BACK to the clients). But if you publish<br>
internal network addresses, it wouldn't be too bad since defining a<br>
route to your internal network is expected. Also, take into<br>
consideration that there may be hosts/addresses in use on the clients'<br>
current network that may use similar addressing schemes. You'd likely<br>
know this before it became and application/sharing problem because<br>
likely you'd overlap on connection, and thus have problems establishing...<br>
<br>
<br>
It can work. It's not easy, prone to mistakes, and, prone to being an<br>
inadvertent entry point into your network.<br>
<br>
There be dragons here.<br>
<br>
bnm<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)<br>
Comment: Using GnuPG with Mozilla - <a href="http://www.enigmail.net/" target="_blank">http://www.enigmail.net/</a><br>
<br>
iQE4BAEBCAAiBQJQosPJGxhoa3A6Ly9rZXlzZXJ2ZXIudWJ1bnR1LmNvbQAKCRD5<br>
XCJY/q4Y6FcEB/9VwZml67U85+nCtJ1m5HJq3BR+vpb2lUxCzhxTxK2Ro8cOXtvF<br>
99hb+kuaeMtl3eEnMKubXnBCoCypjxyKQgzCIJdbIpj6kKoqUOzuxiChGHUNhYjF<br>
oAZHmnwfwkWcwVU0UUwT+hBNRe5ep7QGEMxsgtNju69zeIzjHnTXEhgYdPRQeGz4<br>
n7Hg/hgnxHgsYQFc1xFGqKsov2GZX/IPI2b3YnEt21pzqOZZe9/2r5/fiG3vf4N8<br>
o2dY08TYh0YhuqASx1+WM0qvyPOVcMgTVMU9+Kh8Qnly7HgN5wV4zNnpAjKoG5n4<br>
1IBoaQF3cHVhxOAstxa6ltUUNlWW3nf2R2x2<br>
=XkA+<br>
-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>