On 21 September 2017 at 14:57, James Hogarth <james.hogarth(a)gmail.com>
wrote:
On 21 September 2017 at 09:08, Cristian Sava <csava(a)central.ucv.ro> 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-fedora/
> So the question:
> Is there a tool to simply setup a bridge interface?
>
>
>
>
You can do it in the NetworkManager interface ... but I'm not really sure
what exactly you are asking.
Can you not just script nmcli and call that script to automatically do it
for you each time?
There's an nmcli ansible module you might be able to construct a playbook
with?
http://docs.ansible.com/ansible/latest/nmcli_module.html
Can you be a little more specific with your requirements? If so I'm sure a
more specific and detailed answer can be supplied.
Oh and just a small follow-up from that old article ... the present version
of NetworkManager in EL7 and Fedora do no use special *-slave types and
instead the raw device is just associated with the master... whatever that
is.
See this article for more details:
https://www.hogarthuk.com/?q=node/18
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 connection add type ethernet ifname em1 con-name "System em1" master
br0 connection.autoconnect yes
That's off the top of my head, and a quick check of my blog, but should be
accurate enough to get you going.