Comment # 7 on bug 1032210 from Knut Alejandro Anderssen Gonz�lez

Thnx Tomas,

As commented the main problem is that you are editing a bridge with interfaces
that are not bridgeable from YaST POV. 

Them are not listed because of that and you somehow cheated modifying them
manually to create your bridge, but the way to add them is modifying the
activation of the Device in the "General Tab", after that you will see them as
selectable in the "Bridge Devices" list.

The current (ifpludg) ifcfg documentation is commented until wicked supports
it:

https://github.com/openSUSE/wicked/blob/d40997987ee649ba0c83fabef305eb2b27517cbe/man/ifcfg.5.in#L99

There are some solutions to at least alert the user about the error (I mean
when an interface has been edited/created manually) but need to be discussed,
because the user could also complain if we adapt the configuration
automatically and things like that.

So, I have added it to our incoming board in order to plan for it for next
SCRUM sprints.

** Wicked is the service (framework) selected to manage the network, but is not
the only one, YaST offers you to decide if use it or NetworkManager or disable
the service at all. So to make it simple YaST writes the network configuration
but is wicked (when selected) which read it and configure your network at the
end.