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
In the current version of netclient it wil constantly try to connect to the Broker. And if this fails it wil restart the entire daemon, and as a consequence it wil also disable and renable the WireGuard interfaces. Which can cause an temporary outage.
Would it be possible to only disable/reenable these interfaces when new changes need to be applied. Meaning:
If the deamon restarts, the WireGuard interfaces already exists and the config is correct, the deamon won't touch the WireGuard interfaces.
I would love to know if this could be implemented, this would help immensely in an environment where mqtt/WS-connections can be weird
Version
v0.16.3
What OS are you using?
Linux
Relevant log output
No response
Contributing guidelines
Yes, I did.
The text was updated successfully, but these errors were encountered:
Contact Details
No response
What happened?
In the current version of netclient it wil constantly try to connect to the Broker. And if this fails it wil restart the entire daemon, and as a consequence it wil also disable and renable the WireGuard interfaces. Which can cause an temporary outage.
Would it be possible to only disable/reenable these interfaces when new changes need to be applied. Meaning:
If the deamon restarts, the WireGuard interfaces already exists and the config is correct, the deamon won't touch the WireGuard interfaces.
I would love to know if this could be implemented, this would help immensely in an environment where mqtt/WS-connections can be weird
Version
v0.16.3
What OS are you using?
Linux
Relevant log output
No response
Contributing guidelines
The text was updated successfully, but these errors were encountered: