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
Wishlist: Pushing 'server' directive
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
-
- OpenVpn Newbie
- Posts: 5
- Joined: Fri Dec 13, 2013 12:55 pm
- Traffic
- OpenVPN Protagonist
- Posts: 4066
- Joined: Sat Aug 09, 2014 11:24 am
Re: Wishlist: Pushing 'server' directive
By the sound if this; I think you mean:
- --push "remote {server.ip.address} | {server.dns.name} port proto"
-
- OpenVpn Newbie
- Posts: 5
- Joined: Fri Dec 13, 2013 12:55 pm
Re: Wishlist: Pushing 'server' directive
something like that
- Traffic
- OpenVPN Protagonist
- Posts: 4066
- Joined: Sat Aug 09, 2014 11:24 am
Re: Wishlist: Pushing 'server' directive
Take a look at --setenv-safe in The Manual v23x
-
- OpenVpn Newbie
- Posts: 5
- Joined: Fri Dec 13, 2013 12:55 pm
Re: Wishlist: Pushing 'server' directive
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 ?
is there some extended manual for using custom variables on client's side ?
-
- OpenVpn Newbie
- Posts: 5
- Joined: Fri Dec 13, 2013 12:55 pm
Re: Wishlist: Pushing 'server' directive
--setenv does the same but without prefix. show me the way how to use this feature correctly. please
- Traffic
- OpenVPN Protagonist
- Posts: 4066
- Joined: Sat Aug 09, 2014 11:24 am
Re: Wishlist: Pushing 'server' directive
--setenv is not pushable, only --setenv-safe is ..xeon_greg wrote:setenv does the same
by utilizing the --up script ..xeon_greg wrote:l'll set this: OPENVPN_remote=xxx.xxx.xxx.xxx , how client can use it ?
For example:
Code: Select all
#!/bin/bash
echo $OPENVPN_remote