Wishlist: Pushing 'server' directive

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

Traffic

By the sound if this; I think you mean:

--push "remote {server.ip.address} | {server.dns.name} port proto"

:ugeek:

xeon_greg

something like that

Traffic

Take a look at --setenv-safe in The Manual v23x

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 ?

xeon_greg

--setenv does the same but without prefix. show me the way how to use this feature correctly. please

Traffic

xeon_greg wrotesetenv does the same

--setenv is not pushable, only --setenv-safe is ..

xeon_greg wrotel'll set this: OPENVPN_remote=xxx.xxx.xxx.xxx , how client can use it ?

by utilizing the --up script ..

For example:

#!/bin/bash
echo $OPENVPN_remote