On 4/24/23 17:02, ToddAndMargo via users wrote:
Oh this took my breath away.  The stinking update
trashed my bridge and took out all my qemu-kvm
virtual machines

My notes on how to restore br0:

My better updated notes:

How to add or restore a bridge (br0) when knocked out by an upgrade:

Reference:

https://www.thegeeksearch.com/how-to-configure-network-bridge-in-centos-rhel-7-using-nmcli-command/

https://www.thegeekdiary.com/how-to-create-a-bridge-interface-using-nmcli-in-centos-rhel-7-and-8/

Note: qemu-kvm virtual machines
After restoring, if br0 will not pass traffic in your virtual machines (VM's), go into virt-manager and set the networm interface to comethig else, then set
    it back to br0


Note: to remove a bridge:
   # nmcli con show

   # ip link set br0 down
   # brctl delbr br0
   # nmcli connection delete br0
   # nmcli connection delete br0-port1
   # nmcli connection delete bridge-br0

   Test if you got it with with:
   # nmcli con show
   # brctl show




1. Get a list of the system’s active network connections:

# nmcli conn show --active
NAME                UUID                                  TYPE      DEVICE
Wired connection 1  3bbdbba2-be96-3a0f-b0d5-b8a34912e7b7  ethernet  eno1
virbr0              5ed314a7-f7d5-4719-9f8a-e144718b6288  bridge    virbr

Note: plug something into the eno1, such as teh router to
activate it and do a
    # nmcli device up eno1



2. Next, create a network bridge by typing:

# nmcli conn add type bridge con-name br0 ifname br0
NAME                UUID                                  TYPE      DEVICE
Wired connection 1  3bbdbba2-be96-3a0f-b0d5-b8a34912e7b7  ethernet  eno1
virbr0              5ed314a7-f7d5-4719-9f8a-e144718b6288  bridge    virbr


3. Next, set a static IPv4 address for the bridge network:

Do not set a gateway

# nmcli conn mod br0 ipv4.address '192.168.255.10/24'
########## nmcli conn mod br0 ipv4.gateway '192.168.250.1'
# nmcli conn mod br0 ipv4.method manual


4. Now, add the ethernet interface, eno1, to the bridge, br0, connection:

# nmcli conn add type ethernet slave-type bridge con-name bridge-br0 ifname eno1 master br0 Connection 'bridge-br0' (cb23d052-f04d-4e0b-ae21-18cbc67f1bd6) successfully added.


5. Activate the bridge connection:

# nmcli conn up br0
Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/25)


6. Deactivate the ethernet interface, eno1:

# nmcli conn down eno1
Error: 'eno1' is not an active connection.
Error: no active connection provided.


7. Get a list of the active network connections:

# nmcli conn show --active


8. Display the current bridge port configuration and flags:

# bridge link show
<nothing>

9. Display the new network bridge interface:
# nmcli device up br0
Device 'br0' successfully activated with '8d395a48-3de6-40e8-ad3a-c57aa5f35315'.

# nmcli conn up bridge-br0
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/28)


# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
    link/ether 52:12:34:56:78:5d brd ff:ff:ff:ff:ff:ff
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:12:34:56:78:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.xxx.yy/27 brd 192.168.122.31 scope global noprefixroute br0
       valid_lft forever preferred_lft forever


10:  more info:
# nmcli con show br0



_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to