| Summary: | Unable to bring up the lower interfaces in a bond | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Thiago Macieira <thiago> |
| Component: | Networking in general | Assignee: | Jan Grulich <jgrulich> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | jgrulich, kdedev, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.19.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Patch to fix this issue | ||
|
Description
Thiago Macieira
2020-07-06 16:53:53 UTC
Have you tried opening the KCM, going into configuration and check "Show virtual connections? (In reply to Jan Grulich from comment #1) > Have you tried opening the KCM, going into configuration and check "Show > virtual connections? Yes, that is how I added the upper connection in the first place. The bonded (lower) connections do show up in the editor dialog on the right side (in the Bond tab), but not on the left. That means I can't right-click to activate them. Created attachment 129955 [details]
Patch to fix this issue
We are filtering out the slaves in the model. To be honest I don't know much about bond, bridge or team connections, I assumed they will be always managed by their master connection.
Does the patch make sense to you? It should not filter slaves in case virtual connections are allowed to be shown. And most importantly, does it work?
(In reply to Jan Grulich from comment #3) > Created attachment 129955 [details] > Patch to fix this issue > > We are filtering out the slaves in the model. To be honest I don't know much > about bond, bridge or team connections, I assumed they will be always > managed by their master connection. > > Does the patch make sense to you? It should not filter slaves in case > virtual connections are allowed to be shown. And most importantly, does it > work? That's a good question, I don't know how they should be properly managed in a well-designed UX. I would indeed expect that bringing the controlling layer up enabled the controlled interfaces too, but that's not how NM seems to be behaving. You need to bring each one up. Maybe we do that filtering: if any of the lower interfaces can be enabled, the bond or bridge can be enabled and that's what shows up in the menu. Once you do turn that on, then the other interfaces show up in the menu so you can select which of them you want to turn on (if they're automatic connection, then they get turned on automatically). The patch looks correct for a simple solution to my problem, not what I described. Bulk transfer as requested in T17796 Thanks for the bug report. I'm sorry we weren't able to get to this yet. There have been many fixes and improvements since this was reported, and this issue may have been fixed. Can you please re-test on your system with Plasma 6.4.5 or later and let us know if you can still reproduce the problem? If you can, please set this report back to REPORTED. Thanks! It's still there. |