Hi, On Fri, Jun 05, 2015 at 10:49:48AM -0500, jack seth wrote: > > (As a side note, you're screwed in any case if the hotel gateway happens > > to use an ip address also used by one of your servers - but to fix *that*, > > you'd have to go down the "use NAT on the server tun" route...) > > > Can you further explain the "use NAT on the server tun"? How would you solve > the issue if the server has the same ip address as the hotel gateway? Please > post examples.
Well, if you NAT on the server side (like: present 100.64.x.x as "the
server IP" to the clients, and NAT it to 10.y.x.x inside), the server
no longer "has the same ip address as the hotel gateway", so, solved.
But then of course you have NAT, different IP addresses for the server
depending from which side you look, and all that baggage...
The real solution, of course, is to move to IPv6 and ensure address
uniqueness... private addresses in IPv4 is something from hell. It
looks useful, sneaks into everywhere, and when you notice that it will
break all your designs in nasty ways, it's too late to get rid of it.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgp2QVs3r8US0.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
