Page 1 of 1
Wishlist: Pushing 'server' directive
Posted: Thu Sep 24, 2015 7:16 am
by xeon_greg
It would be great to push 'server' directive to clients. That clients could store it somewhere for further connections, and remove old unusable server addresses
DNS using is very inconvenient, caching time, having DNS itself and so on
Re: Wishlist: Pushing 'server' directive
Posted: Thu Sep 24, 2015 4:49 pm
by Traffic
By the sound if this; I think you mean:
- --push "remote {server.ip.address} | {server.dns.name} port proto"

Re: Wishlist: Pushing 'server' directive
Posted: Sat Sep 26, 2015 8:39 am
by xeon_greg
something like that
Re: Wishlist: Pushing 'server' directive
Posted: Sat Sep 26, 2015 9:48 am
by Traffic
Take a look at --
setenv-safe in
The Manual v23x
Re: Wishlist: Pushing 'server' directive
Posted: Sat Sep 26, 2015 11:38 am
by xeon_greg
ok, suppose l'll set this: OPENVPN_remote=xxx.xxx.xxx.xxx , how client can use it ?. and how to exclude one of the old 'remote' directive on the client side.
is there some extended manual for using custom variables on client's side ?
Re: Wishlist: Pushing 'server' directive
Posted: Sat Sep 26, 2015 11:41 am
by xeon_greg
--setenv does the same but without prefix. show me the way how to use this feature correctly. please
Re: Wishlist: Pushing 'server' directive
Posted: Sat Sep 26, 2015 12:19 pm
by Traffic
xeon_greg wrote:setenv does the same
--
setenv is
not pushable, only --
setenv-safe is ..
xeon_greg wrote:l'll set this: OPENVPN_remote=xxx.xxx.xxx.xxx , how client can use it ?
by utilizing the --
up script ..
For example: