Repairing VM network connections after upgrade to Leap 15.6

I have at last been able to upgrade to 156 but in getting there my Network Manager configuration had been totally munged and I had to clean out all the configuration files and start over.

I now have a working internet network connection and have two nics enabled. I have followed the instructions I had from Malcolm last year on using nmtui to set up a bridge using my second nic connection for use on VM

Sadly I am not getting any internet connection on the VM. This is what I have on my machine:-

alastair@localhost:~> ip a
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
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:40:b5:93:38:d0 brd ff:ff:ff:ff:ff:ff
    altname eno1
    altname enp11s0f0
    inet 192.168.169.134/25 brd 192.168.169.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::e21c:90e1:6936:149a/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:40:b5:93:38:d1 brd ff:ff:ff:ff:ff:ff
    altname eno2
    altname enp11s0f1
    inet 192.168.169.205/25 brd 192.168.169.255 scope global dynamic noprefixroute eth1
       valid_lft 76244sec preferred_lft 76244sec
    inet6 fe80::ee77:65fe:88f0:fae1/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000
    link/ether 36:40:b5:93:38:d5 brd ff:ff:ff:ff:ff:ff
    altname enp0s26f1u2
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 36:40:b5:93:38:d5 brd ff:ff:ff:ff:ff:ff
    inet 169.254.95.120/24 brd 169.254.95.255 scope link dynamic noprefixroute br0
       valid_lft 998sec preferred_lft 998sec
    inet6 fe80::d900:e6dd:7f78:544f/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
alastair@localhost:~> 

and here are my NM connections:-

alastair@localhost:~> nmcli
eth0: connected to MainEthernet
        "Broadcom and subsidiaries NetXtreme II BCM5716"
        ethernet (bnx2), 34:40:B5:93:38:D0, hw, mtu 1500
        ip4 default
        inet4 192.168.169.134/25
        route4 192.168.169.128/25 metric 100
        route4 192.168.169.128/25 via 192.168.169.129 metric 100
        route4 default via 192.168.169.129 metric 100
        inet6 fe80::e21c:90e1:6936:149a/64
        route6 fe80::/64 metric 1024

br0: connected to Bridge connection 1
        "br0"
        bridge, 36:40:B5:93:38:D5, sw, mtu 1500
        inet4 169.254.95.120/24
        route4 169.254.95.0/24 metric 425
        inet6 fe80::d900:e6dd:7f78:544f/64
        route6 fe80::/64 metric 1024

eth1: connected to WiredSecondConnection
        "Broadcom and subsidiaries NetXtreme II BCM5716"
        ethernet (bnx2), 34:40:B5:93:38:D1, hw, mtu 1500
        inet4 192.168.169.205/25
        route4 192.168.169.128/25 metric 101
        route4 default via 192.168.169.129 metric 101
        inet6 fe80::ee77:65fe:88f0:fae1/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

vnet0: connected (externally) to vnet0
        "vnet0"
        tun, FE:54:00:00:4F:F5, sw, mtu 1500
        master br0
        inet6 fe80::fc54:ff:fe00:4ff5/64
        route6 fe80::/64 metric 256

usb0: connected to Ethernet connection 1
        "IBM RNDIS/CDC ETHER"
        ethernet (cdc_ether), 36:40:B5:93:38:D5, hw, mtu 1500
        master br0

DNS configuration:
        servers: 192.168.169.129 192.168.1.1
        interface: eth0

        servers: 192.168.169.129 192.168.1.1
        interface: eth1

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
lines 20-57/57 (END)

Please can somebody please help me sort this out.

@Budgie2 You need to disable ipv4 and ipv6 on the bridge device and reboot. It has IP addresses…

It should be like;

br0: connected to Bridge connection 0
        "br0"
        bridge, 0E:24:64:BC:43:76, sw, mtu 1500

enp10s0: connected to br0 port 1
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), 88:C9:B3:BF:07:B4, hw, mtu 1500
        controller br0

Without knowing how your VM are (supposed to be) connected it is impossible to guess what is wrong.

So what? Nothing prevents having IP address on a bridge. Actually, this is what most people use anyway when host and VM are sharing the same bridge.

And it is incorrect - the bridge does NOT have an IP address - it only has link local APIPA address. Which is not surprising as this bridge does not have any external connection at all, it only has a single slave vnet0. Probably, it is interface from VM and then this VM does not have external connectivity. But this is just a guess.

It doesn’t look like usb0 is working. Are you sure this is the network interface you want to bridge to?

I believe I have corrected my errors, at least to the extent that my VM W10 is running but I cannot get any internet connection on the VM. Here is what I have now for ip address and nmcli:-

alastair@localhost:~> ip a
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
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:40:b5:93:38:d0 brd ff:ff:ff:ff:ff:ff
    altname eno1
    altname enp11s0f0
    inet 192.168.169.134/25 brd 192.168.169.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::e21c:90e1:6936:149a/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:40:b5:93:38:d1 brd ff:ff:ff:ff:ff:ff
    altname eno2
    altname enp11s0f1
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 36:40:b5:93:38:d5 brd ff:ff:ff:ff:ff:ff
    altname enp0s26f1u2
    inet 169.254.95.120/24 brd 169.254.95.255 scope link dynamic noprefixroute usb0
       valid_lft 975sec preferred_lft 975sec
    inet6 fe80::79c3:1dee:1e50:df91/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
11: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether fe:54:00:00:4f:f5 brd ff:ff:ff:ff:ff:ff
12: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:00:4f:f5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe00:4ff5/64 scope link proto kernel_ll 
       valid_lft forever preferred_lft forever
alastair@localhost:~> 

and:-

alastair@localhost:~> nmcli
eth0: connected to Main Ethernet Connection
        "Broadcom and subsidiaries NetXtreme II BCM5716"
        ethernet (bnx2), 34:40:B5:93:38:D0, hw, mtu 1500
        ip4 default
        inet4 192.168.169.134/25
        route4 192.168.169.128/25 metric 100
        route4 192.168.169.128/25 via 192.168.169.129 metric 100
        route4 default via 192.168.169.129 metric 100
        inet6 fe80::e21c:90e1:6936:149a/64
        route6 fe80::/64 metric 1024

usb0: connected to Second connection
        "IBM RNDIS/CDC ETHER"
        ethernet (cdc_ether), 36:40:B5:93:38:D5, hw, mtu 1500
        inet4 169.254.95.120/24
        route4 169.254.95.0/24 metric 101
        inet6 fe80::79c3:1dee:1e50:df91/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

vnet0: connected (externally) to vnet0
        "vnet0"
        tun, FE:54:00:00:4F:F5, sw, mtu 1500
        master br0
        inet6 fe80::fc54:ff:fe00:4ff5/64
        route6 fe80::/64 metric 256

br0: connected to Bridge connection 1
        "br0"
        bridge, FE:54:00:00:4F:F5, sw, mtu 1500

eth1: disconnected
        "Broadcom and subsidiaries NetXtreme II BCM5716"
        1 connection available
        ethernet (bnx2), 34:40:B5:93:38:D1, hw, mtu 1500

DNS configuration:
        servers: 192.168.169.129 192.168.1.1
        interface: eth0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
lines 6-49/49 (END

I have no idea why my prompt shows me logged alastair@localhost but this msut be from an artefact from my earlier problem and upgrade.

Regarding usb0 this is a built-in connection from IBM firmware to give subscribers direct access. It is no longer required and at some point I need to find out how to disable it.

Regarding arvidjaar’s comment it does appear that my VM does not have external connectivity. The VM is Windows 10 on QEMU/KVM. What I have been trying to do is use the second nic connection only for VM traffic and not for connection to my system directly but this may not be feasible. I have had this working in the past but after my upgrade my rebuild clearly has mistakes.

Now you have only the vnet0 in bridge br0.
If you want to use the eth0 in bridge run this: sudo nmcli con add type bridge-slave ifname eth0 master br0

@Budgie2 I reiterate that none of my interaces, bridges or vnet devices have an ipv4 or ipv6 addresses;

br0: connected to Bridge connection 0
        "br0"
        bridge, 0E:24:64:BC:43:76, sw, mtu 1500

br1: connected to Bridge connection 1
        "br1"
        bridge, AE:94:C8:51:CA:7B, sw, mtu 1500

br2: connected to Bridge connection 2
        "br2"
        bridge, DE:B7:10:99:4A:02, sw, mtu 1500

br3: connected to Bridge connection 3
        "br3"
        bridge, 2E:59:F2:37:BE:3A, sw, mtu 1500

enp10s0: connected to br0 port 1
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), 88:C9:B3:BF:07:B4, hw, mtu 1500
        controller br0

enp11s0: connected to br1 port 1
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), 88:C9:B3:BF:07:B5, hw, mtu 1500
        controller br1

enp12s0: connected to br2 port 1
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), 88:C9:B3:BF:07:B6, hw, mtu 1500
        controller br2

enp13s0: connected to br3 port 1
        "Realtek RTL8111/8168/8211/8411"
        ethernet (r8169), 88:C9:B3:BF:07:B7, hw, mtu 1500
        controller br3

vnet0: connected (externally) to vnet0
        "vnet0"
        tun, FE:54:00:3C:17:E4, sw, mtu 1500
        controller br0

vnet1: connected (externally) to vnet1
        "vnet1"
        tun, FE:54:00:E4:AA:C1, sw, mtu 1500
        controller br1

2: enp10s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
    link/ether 88:c9:b3:bf:07:b4 brd ff:ff:ff:ff:ff:ff
4: enp11s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br1 state UP group default qlen 1000
    link/ether 88:c9:b3:bf:07:b5 brd ff:ff:ff:ff:ff:ff
5: enp12s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br2 state UP group default qlen 1000
    link/ether 88:c9:b3:bf:07:b6 brd ff:ff:ff:ff:ff:ff
6: enp13s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br3 state UP group default qlen 1000
    link/ether 88:c9:b3:bf:07:b7 brd ff:ff:ff:ff:ff:ff
7: br3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 2e:59:f2:37:be:3a brd ff:ff:ff:ff:ff:ff
8: br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ae:94:c8:51:ca:7b brd ff:ff:ff:ff:ff:ff
9: br2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether de:b7:10:99:4a:02 brd ff:ff:ff:ff:ff:ff
10: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 0e:24:64:bc:43:76 brd ff:ff:ff:ff:ff:ff
11: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:3c:17:e4 brd ff:ff:ff:ff:ff:ff
12: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br1 state UNKNOWN group default qlen 1000

I do have ipv6 disabled as well as forwarding set for ipv4;

net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 0
net.ipv6.conf.all.disable_ipv6 = 1

Hi Heitor,
Many thanks. Actually I have used eth1 for the bridge and this is now working fine. Much to learn from man pages! Her eis waht I have now:-

alastair@localhost:~> nmcli
eth0: connected to Main Ethernet Connection
        "Broadcom and subsidiaries NetXtreme II BCM5716"
        ethernet (bnx2), 34:40:B5:93:38:D0, hw, mtu 1500
        ip4 default
        inet4 192.168.169.134/25
        route4 192.168.169.128/25 metric 100
        route4 192.168.169.128/25 via 192.168.169.129 metric 100
        route4 default via 192.168.169.129 metric 100
        inet6 fe80::e21c:90e1:6936:149a/64
        route6 fe80::/64 metric 1024

usb0: connected to Second connection
        "IBM RNDIS/CDC ETHER"
        ethernet (cdc_ether), 36:40:B5:93:38:D5, hw, mtu 1500
        inet4 169.254.95.120/24
        route4 169.254.95.0/24 metric 101
        inet6 fe80::79c3:1dee:1e50:df91/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet4 127.0.0.1/8
        inet6 ::1/128

br0: connected to Bridge connection 1
        "br0"
        bridge, 34:40:B5:93:38:D1, sw, mtu 1500

eth1: connected to bridge-slave-eth1
        "Broadcom and subsidiaries NetXtreme II BCM5716"
        ethernet (bnx2), 34:40:B5:93:38:D1, hw, mtu 1500
        master br0

DNS configuration:
        servers: 192.168.169.129 192.168.1.1
        interface: eth0

Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.

Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
alastair@localhost:~> 

This has enabled my VM again but still some questions. New to me:-

lo: connected (externally) to lo

Why externally?

And on the usb0 connection,

usb0: connected to Second connection

As far as I am concerned this connection comes from the IBM firmware. I think I need to disable it as it is of no use and I assume leaves unwanted ports open. How can I disable this?

Finally, for Malcolm, I do not understand what you are saying here. If none of your interfaces have any ipv4 or ipv6 addresses, how do you communicate with the WAN? I must be missing more than I thought but thanks anyhow.

@Budgie2 The virtual machines are either dhcp or static with there own e1000e interface(s) setup in the VM to use brN.

'Externally" means that this interface has not been configured by NetworkManager (and no connection definition matching the current interface configuration exists).

The “connection” cannot come from the firmware. The “connection” only exists in the NetworkManager configuration. I already tried to explain it to you more than once, but you do not listen.

I have been imprecise. I should have asked why is this connection there at all?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.