You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Show a warning in VPN > IPsec > Connections if any *conf files are found in /usr/local/etc/swanctl/conf.d/
Is your feature request related to a problem? Please describe.
/usr/local/etc/swanctl/conf.d/*.conf overrides what is configured in the GUI
Describe the solution you like
Show a warning in VPN > IPsec > Connections area of UI when any files are found, that what you are setting in UI may or may not be overridden by manually created config files.
Describe alternatives you considered
Management of *.conf files through GUI - ability to upload/download/text-edit/disable/enable specific fragments. This would be a lot more work to implement. And probably still require the same warning anyway!
Additional context
The VPN documentation section "Custom configurations" is not clear about what is required. No examples are given.
The text was updated successfully, but these errors were encountered:
It would be the better approach to tell what is missing so it can be added to the GUI if possible, to avoid custom configuration files for as many users as possible.
Thank you for creating an issue.
Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.
Show a warning in VPN > IPsec > Connections if any *conf files are found in /usr/local/etc/swanctl/conf.d/
Is your feature request related to a problem? Please describe.
/usr/local/etc/swanctl/conf.d/*.conf overrides what is configured in the GUI
Describe the solution you like
Show a warning in VPN > IPsec > Connections area of UI when any files are found, that what you are setting in UI may or may not be overridden by manually created config files.
Describe alternatives you considered
Management of *.conf files through GUI - ability to upload/download/text-edit/disable/enable specific fragments. This would be a lot more work to implement. And probably still require the same warning anyway!
Additional context
The VPN documentation section "Custom configurations" is not clear about what is required. No examples are given.
The text was updated successfully, but these errors were encountered: