[FIXED] "Infinitely resolve server" checkbox doesn't change anything. Bug?
-
On 2.3.4 Release.
In OpenVPN client configuration, there's a checkbox labeled "Server hostname resolution - Infinitely resolve server" but it seems to make no difference to the configuration whether it's checked or not.
Looking at /var/etc/openvpn/client1.conf:
When not checked:
resolv-retry infinite
^ You'd think this directive would be removed when the checkbox is unchecked.
When checked:
resolv-retry infinite
^ Directive is there as expected.
-
My guess is that gui option is being removed and they forgot to remove it from the gui ;)
I am on the 2.4 beta and while
resolv-retry infinite
Is in the client config.. There is no checkbox in the client gui config to check or uncheck that I see?
-
It was fixed recently: https://redmine.pfsense.org/issues/7572
-
Honestly, it'd be nice for more granular control of the .ovpn config file via the GUI (i.e., the entire config). For example, persist-key and persist-tun and resolv-retry-infinite are simply hard-coded now, and if we manually edit the text file, it gets overwritten whenever the Service restarts.
My pipe dream would be a GUI that dynamically builds the config file, but there's a drop-down element for "every" possible directive. This would take a lot of coding probably.
Or an easier option: Simply create an "Advanced Mode" in the GUI that lets us have 100% control over the config file without inserting anything.
-
Honestly, it'd be nice for more granular control of the .ovpn config file via the GUI (i.e., the entire config). For example, persist-key and persist-tun and resolv-retry-infinite are simply hard-coded now, and if we manually edit the text file, it gets overwritten whenever the Service restarts.
My pipe dream would be a GUI that dynamically builds the config file, but there's a drop-down element for "every" possible directive. This would take a lot of coding probably.
Or an easier option: Simply create an "Advanced Mode" in the GUI that lets us have 100% control over the config file without inserting anything.
My sentiments exactly.
One of my pet peeves is partially implemented features/capabilities etc. That's why I did the advanced option for DHCP client a few years ago. Nearly everything is settable via the GUI advanced options. But for the rare cases of something not being there or a bug, etc. A config file override option is available to put a DHCP client config file anywhere you please and point the GUI config at it.
