|
|
On Thu, 4 Nov 2004, Adam Pavelec wrote: > >> If you use persist-tun on the client, you can avoid any routing > >> changes after the network comes back up after an outage. > > > Thanks -- I'll give it a shot. > > When I run my client with persist-tun, I get the following > warning: > > WARNING: using a --persist option may conflict with --pull You will get this warning with 2.0-beta11 and earlier, as the --persist-tun code has some issues when being used with --pull. For example, suppose that --persist-tun has been specified, but on restart the server (via --pull) wants to give the client a new IP address? There's a potential conflict here. In beta12 and later, the --persist-tun code on the client is smarter and will only persist the state of the currently open TUN/TAP interface on restart if the new pull from the server produces an identical configuration. To help encourage the server not to change the configuration of a client which connects multiple times, beta12 and higher on the server has the --ifconfig-pool-persist option as well. James ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |