tested and resolved, we've added this change in our cli to fix this deprecate option in opnvpn :
[edit] vyos@vyos-ser-win# set interfaces openvpn vtun10 server topology Possible completions: subnet Subnet topology (recommended) (default) point-to-point Point-to-point topology net30 net30 topology (deprecated)
Time of task extended for testing.
Tested in 1.4.0 version and did not receive the error:
This uncovered another issue, once an interface is removed from the system,
Imho, this should be reflected in the documentation, at least; Ideally with an example for how to import the most recent ACME intermediates.
Hi, I’d be happy to take this on.
I've tested in the new version , the problem with default net30 , it is already there .however , when the new version started show a warning message that migrating from net30 to subnet because is going to be deprecated :
The solution sketched above will be handled in subtask T6569; in this task we will revert to using only the local redundancy removal in order to provide per-script error reporting.
Recovering gracefully and logging an error is a simple fix, and will be committed in the interim while the larger issue is addressed: namely, when running under vyos-configd, a ConfigError in a called dependency script should elicit a commit error in the originating config session. Here, however, we confront again the constraints of operating under the legacy commit algorithm. To address the matter, we will implement a partial solution to T5731 so as to catch verification errors in the (first instance of) sequential processing of the priority queue and cache the data for final processing of the activation stages (generate/apply); errors in the latter stages, as less common, will be logged. The sketch provided summarizes a design that balances the needs of early and correct (verify stage) error reporting with removing redundancy overhead when running under configd.