|
|
Darren Spruell wrote: Not in the client/server model from 1.6 ( haven't worked with the 2.0 series yet ). Only the client needs to know the IP of the server. The server couldn't care less about where the client's calling from.We would like to set up a branch office VPN connection between two sites. One endpoint is a Linux firewall with an Internet-routable IP, the other endpoint is a Linux server behind a NAT firewall and has an RFC1918 IP address. We would hope that this would work correctly if the connection is initiated from the Linux server behind the NAT box to the other firewall with the public address; return traffic would simply be routed back to the NAT box and translated to the server again. At least, that's how i have it setup. I have 3 clients on dynamic IPs, which change quite frequently. I've never had an issue. Further, I have a client coming from behind a linksys home gateway router thingy ( win2k client ), and she hasn't had any issues either ( thank god ). One thing possibly worth noting, and something you probably already know: Because openvpn uses udp, your firewall may have issues with it. That all depends on the firewall of course, some are more intelligent than others. Just set openvpn to ping every x seconds, and you should be ok. ( again, sorry if you already knew this, but I'm adding in here for future searchability ) Sean
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-01/msg00041.html on line 209 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-01/msg00041.html on line 209 |