On Thu, 2017-09-21 at 23:54 -0700, Samuel Sieb wrote:
On 09/21/2017 11:30 PM, Cristian Sava wrote:
> To be more precise, I expect something really simple like:
> nmcli tobridge ifcfg-eth0
> nothing more, instead of the two complicated lines, because all
> configuration is already in ifcfg-eth0 and the bridge will be build
> from that.
How is there enough information in there to create a bridge since
only information in that file is to configure an ethernet interface.
Directly from my F27 (thanks Fedora team!) workstation that hosts
[cristi@s222 network-scripts]$ cat ifcfg-enp0s25
[cristi@s222 network-scripts]$ cat ifcfg-bridge0
I think it's clear enough that you have all you need to go from ifcfg-
enp0s25 to ifcfg-enp0s25 & ifcfg-bridge0 and also do a reverse thing.
> It should also be an option at install time to choose bridge
> normal ethernet.
What use would a bridge be for installing? I can understand maybe a
vlan config but not a bridge.
NO. You have a server or workstation with virtual boxes with IPs to
connect to. So you have to switch to a bridge your normal interface of
> As of now we have no option to do that in the graphical network
> configuration tool!
Yes, you have to know and install it.
> So, I know how to do that but it's not easy for average user
> a problem to be solved.
Why would an average user have any use at all for this?
Because you want to
integrate (and connect to) his virtual box.
I don't even understand from your original question what it is
trying to do.
You have a physical box and you want a web server and a mail server on
it. So you will put one in a virtual box.
You have a workstation and you need wine in a different box and
accessed from around stations.