Opened 4 years ago
Closed 4 years ago
#1307 closed User question (worksforme)
Allow --tls-exit to be used in a <connection> block
Reported by: | tct | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | |
Component: | Configuration | Version: | |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | connection fail exit |
Cc: |
Description
The aim is to try all servers in a list and exit if all fail.
This would allow the following:
<connection> remote main.server 1194 </connection> <connection> remote backup.server 1195 tls-exit </connection>
This configuration will not load because --tls-exit
cannot be used in a <connection>
block.
I also tried:
<connection> remote main.server 1194 </connection> tls-exit <connection> remote backup.server 1195 </connection>
This configuration will load but --tls-exit
causes openvpn to exit after the first failure and not try the second <connection>
block.
Alternatively, a new option but I know how new options are not popular.
I cannot find a way to do the scenario above.
Perhaps this is a design decision, if so, could the decision be re-visited or explained?
Change History (1)
comment:1 Changed 4 years ago by
Component: | Generic / unclassified → Configuration |
---|---|
Priority: | minor → trivial |
Resolution: | → worksforme |
Status: | new → closed |
Type: | Feature Wish → User question |
Note: See
TracTickets for help on using
tickets.
After reading and testing, I realised that this is exactly what
--connect-retry-max 1
does.