-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to set ipv4.may-fail / ipv6.may-fail #735
Comments
I just realized that this is the wrong setting to change. |
In NetworkManager, |
The PR for supporting |
Amazing! Thanks a lot @liangwen12year 🎉 |
@Hoeze , |
Oh, I see, then I misunderstood this option. Thank you for the explanation. Would you be able to also support the |
yes, I can support it. By the way, |
The property in
Here is an example:
@Hoeze , can you try out the |
Thanks a lot @liangwen12year! It's amazing to have these features so fast available :) Reguarding your suggestion, I did not have time to test it yet. But #741 makes it unnecessary, right? |
Right. you can achieve the similar effect by using the may_fail4 or may_fail6 in the network_connections variable. |
Hi, I am trying to setup a persistent bridge with networkmanager but the bridge connection gets deactivated once it fails to configure IPv4.
Networkmanager allows to set "ipv4.may-fail" and "ipv6.may-fail" to keep the connection up even when the ip configuration fails.
Is it possible to set these options with this role?
If not, would it be possible to add these options?
The text was updated successfully, but these errors were encountered: