| Summary: | Bridge connection not work | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | mah454 <mahsom> |
| Component: | Networking in general | Assignee: | Lukáš Tinkl <lukas> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | goo, jgrulich |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
mah454
2014-11-13 07:54:29 UTC
I can confirm that slave interfaces are not enslaved on the master interface. # nmcli con up bridge-1 Error: Device 'br1' is waiting for slaves before proceeding with activation Furthermore it is not possible to add slave interfaces to the the master bridge interface as the connection editor window doesn't permit to select any active interface to add it as a slave. running plasma-nm 5.2.2 Unfortunately I don't have any idea how to solve this issue, because we implemented it according to the original nm-connection-editor, where you cannot also select an active interface, but only create a new slave which needs to be activated first (I guess). I'll check how this is supposed to work when I have more time. Truth is that bridge/bond/team connections haven't been properly tested and we were just assuming that they work. Any help with those types of connections is welcomed, especially when you have better knowledge than me. Closing, we don't support bridge connections anymore as our focus is primary on desktop. Bulk transfer as requested in T17796 |