On Fri, 2017-09-22 at 08:38 -0700, Gordon Messmer wrote:
> On 09/21/2017 11:30 PM, Cristian Sava wrote:
> > Why do I need to specify this long list of parameters for basic
> > things?
>
>
> If you're doing this for virtualization purposes (as opposed to
> creating
> a network bridge with multipl
On 09/21/2017 11:30 PM, Cristian Sava wrote:
Why do I need to specify this long list of parameters for basic things?
If you're doing this for virtualization purposes (as opposed to creating
a network bridge with multiple interfaces), the simpler answer is:
virsh iface-bridge eth0 br0 --n
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 if
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
On Thu, 2017-09-21 at 15:31 +0100, James Hogarth wrote:
>
>
> If you have an existing connection of "System em1" for instance the
> quickest way to turn that into a bridge with a device name of br0 is
> now:
>
> nmcli connection add type bridge ifname br0 con-name "System bridge"
> nmcli connect
On 21 September 2017 at 14:57, James Hogarth
wrote:
>
>
> On 21 September 2017 at 09:08, Cristian Sava wrote:
>
>> Hi all,
>>
>> Some of us choose to build Fedora servers (instead of using Centos, for
>> vary reasons) with many virtuals, each with different IP.
>> Everytime I have to follow thes
On 21 September 2017 at 09:08, Cristian Sava wrote:
> Hi all,
>
> Some of us choose to build Fedora servers (instead of using Centos, for
> vary reasons) with many virtuals, each with different IP.
> Everytime I have to follow these guidelines
> https://fedoramagazine.org/build-network-bridge-fed