trying to configure teamed bridge for VM...

Issues related to configuring your network
Post Reply
pseud
Posts: 15
Joined: 2018/01/27 15:58:42

trying to configure teamed bridge for VM...

Post by pseud » 2020/01/26 04:48:41

Hello Folks

I'm at my wits end.
This morning I had:
lan <> eth <> bridge (IP) <> VM (IP)
Now I have:
lan <> eth <>team <> bridge (IP) | VM
The reason for the team is there's another wifi device to be added in addition to eth
I was following this cookbook:
https://spottedhyena.co.uk/centos-8-tea ... ing-nmcli/

Also, probably completely unrelated, I'm no longer able to login to ether of my VMs via the virtual console in virt-manager or the cockpit VM consoles, either as root or as user (admin & ncadmin). I have 4 logins in 2 VMs each with the same password and I'm unable to login to any - I guess there must be some keyboard layout chage, but I have absolutely no idea.

This is the relevant part (afaik) of virsh dumpxml from 24.11.19:

Code: Select all

    <interface type='bridge'>
      <mac address='52:54:00:0d:a3:9a'/>
      <source bridge='nm-bridge1'/>
      <target dev='vnet1'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
And the relevant part from today:

Code: Select all

    <interface type='bridge'>
      <mac address='52:54:00:0d:a3:9a'/>
      <source bridge='nm-bridge1'/>
      <target dev='vnet1'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
They look about the same to me...
Also attached my config under /etc/sysconfig/network-scripts. (grr - Add files: invalid file extension... fixed)

If anyone's able to shed some light on this trouble, it would be very much appreciated.

Thx
Attachments
ifcfg-team-slave-ens1.txt
(181 Bytes) Downloaded 10 times
ifcfg-team1.txt
(198 Bytes) Downloaded 9 times
ifcfg-Bridge_connection_1.txt
(318 Bytes) Downloaded 6 times
Morgan Read

pseud
Posts: 15
Joined: 2018/01/27 15:58:42

Re: trying to configure teamed bridge for VM...

Post by pseud » 2020/01/26 04:50:22

ifcfg-Wired_connection_1.txt
(304 Bytes) Downloaded 7 times
Morgan Read

hunter86_bg
Posts: 2015
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: trying to configure teamed bridge for VM...

Post by hunter86_bg » 2020/01/27 20:45:56

Your team device needs TEAM_CONFIG or it will never work.
There are samples somewhere in '/usr/share/doc/teamd-<version>/example_configs'
Copy one of them, edit and update your team device.

pseud
Posts: 15
Joined: 2018/01/27 15:58:42

Re: trying to configure teamed bridge for VM...

Post by pseud » 2020/02/02 21:09:30

hunter86_bg wrote:
2020/01/27 20:45:56
Your team device needs TEAM_CONFIG or it will never work.
Thank you Hunter

I thought I was getting this sorted, but see the begining of my post as quoted at bottom for a brief update on progress since last week.

Then I delete vnet0 from within nm-bridge0 via nmtui - and all the vnet#s lost their IPs and appear disconnected from nm-bridge0. Back to square-one!!! Trying to reconnect has become a nightmare: rebooting VM's and hardware seems futile. Below is the out put from setting up the vnet#s again - but, without success - there seems to be a problem related to some old bugs and some missing or misconfigured config files: 'error: Failed to list interfaces
error: internal error: failed to get number of host interfaces: unspecified error - errors in loading some config files'. See links below.

Code: Select all

virsh # attach-interface VortexBox25 bridge nm-bridge1 --target vnet1 --model virtio --config
Interface attached successfully

virsh # attach-interface Nextcloud bridge nm-bridge1 --target vnet0 --model virtio --config
Interface attached successfully

virsh #
Seems to work, this is what ifconfig now shows:

Code: Select all

# ifconfig
...
nm-bridge1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.20  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::3c59:20f:dfba:7d02  prefixlen 64  scopeid 0x20<link>
        ether 00:16:d4:3f:9b:1d  txqueuelen 1000  (Ethernet)
        RX packets 2491  bytes 203125 (198.3 KiB)
        RX errors 0  dropped 546  overruns 0  frame 0
        TX packets 1089  bytes 394441 (385.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nm-team1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:16:d4:3f:9b:1d  txqueuelen 1000  (Ethernet)
        RX packets 2511  bytes 185908 (181.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1379  bytes 430188 (420.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::fc54:ff:feba:c962  prefixlen 64  scopeid 0x20<link>
        ether fe:54:00:ba:c9:62  txqueuelen 1000  (Ethernet)
        RX packets 109  bytes 22399 (21.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1781  bytes 113499 (110.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::fc54:ff:fe0d:a39a  prefixlen 64  scopeid 0x20<link>
        ether fe:54:00:0d:a3:9a  txqueuelen 1000  (Ethernet)
        RX packets 28  bytes 4776 (4.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1846  bytes 130232 (127.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
...
And, I can ping ip6 from the host:

Code: Select all

# ping -6 fe80::fc54:ff:feba:c962
PING fe80::fc54:ff:feba:c962(fe80::fc54:ff:feba:c962) 56 data bytes
64 bytes from fe80::fc54:ff:feba:c962%vnet0: icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from fe80::fc54:ff:feba:c962%vnet0: icmp_seq=2 ttl=64 time=0.071 ms
64 bytes from fe80::fc54:ff:feba:c962%vnet0: icmp_seq=3 ttl=64 time=0.079 ms
^C
--- fe80::fc54:ff:feba:c962 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 28ms
rtt min/avg/max/mdev = 0.071/0.078/0.086/0.011 ms
[root@frontserver ~]# ping -6 fe80::fc54:ff:fe0d:a39a
PING fe80::fc54:ff:fe0d:a39a(fe80::fc54:ff:fe0d:a39a) 56 data bytes
64 bytes from fe80::fc54:ff:fe0d:a39a%vnet1: icmp_seq=1 ttl=64 time=0.069 ms
64 bytes from fe80::fc54:ff:fe0d:a39a%vnet1: icmp_seq=2 ttl=64 time=0.078 ms
64 bytes from fe80::fc54:ff:fe0d:a39a%vnet1: icmp_seq=3 ttl=64 time=0.074 ms
^C
--- fe80::fc54:ff:fe0d:a39a ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 32ms
rtt min/avg/max/mdev = 0.069/0.073/0.078/0.010 ms
# virsh domiflist Nextcloud
Interface  Type       Source     Model       MAC
-------------------------------------------------------
vnet1      bridge     nm-bridge1 virtio      52:54:00:0d:a3:9a

# virsh domiflist VortexBox25
Interface  Type       Source     Model       MAC
-------------------------------------------------------
vnet0      bridge     nm-bridge1 virtio      52:54:00:ba:c9:62

#
But, not from lan (which might be more about my lan).

And, virsh net-list shows nil IPs:

Code: Select all

# virsh net-list
 Name                 State      Autostart     Persistent
----------------------------------------------------------

#
Which doesn't seem right. And neither does the following:

Code: Select all

virsh net-dumpxml vnet1
error: failed to get network 'vnet1'
error: Network not found: no network with matching name 'vnet1'

# virsh iface-list
error: Failed to list interfaces
error: internal error: failed to get number of host interfaces: unspecified error - errors in loading some config files

#
And, ncftool list shows similar errors:

Code: Select all

# ncftool list
error: unspecified error
error: errors in loading some config files
#
Investigating online throws up some old bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=826752
https://alioth-lists.debian.net/piperma ... 05004.html
https://lists.ubuntu.com/archives/ubunt ... 40204.html
https://www.mail-archive.com/search?l=u ... newest&f=1

I have been unable to correct the problem with reference to the above bugs - what config files where might misconfigured or missing?

I hope someone is able to shed some light?
Many thanks.

hunter86_bg wrote:
2020/01/27 20:45:56
Your team device needs TEAM_CONFIG or it will never work.
Thank you Hunter

After leaving it for a week, destroying everything in network-scripts (except for the bridge which was the only thing hanging on to my VMs) and building everything from the hardware IFs up it's now working again - it took some reboots of VMs and hardware before the vlan#s found any attraction to the bridge, but now I have 3 vlan#s where once I had 2 - better too many than too few, I guess. A bit too much like black magic for my comfort.

I'm now able to login again with key based ssh - too much confusion between US and UK keyboards in my house to rely on passwords...

But, the virtual networks are still weird:
# virsh net-list
Name State Autostart Persistent
----------------------------------------------------------

#
But:
# ifconfig
...
vnet0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether be:e0:0c:02:bf:c4 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:fe0d:a39a prefixlen 64 scopeid 0x20<link>
ether fe:54:00:0d:a3:9a txqueuelen 1000 (Ethernet)
RX packets 145720 bytes 22958582 (21.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 516125 bytes 49271334 (46.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vnet2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:feba:c962 prefixlen 64 scopeid 0x20<link>
ether fe:54:00:ba:c9:62 txqueuelen 1000 (Ethernet)
RX packets 2400347 bytes 4929264948 (4.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4425568 bytes 2490479501 (2.3 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

And:
# ping -6 fe80::fc54:ff:feba:c962
PING fe80::fc54:ff:feba:c962(fe80::fc54:ff:feba:c962) 56 data bytes
64 bytes from fe80::fc54:ff:feba:c962%vnet2: icmp_seq=1 ttl=64 time=0.068 ms
64 bytes from fe80::fc54:ff:feba:c962%vnet2: icmp_seq=2 ttl=64 time=0.081 ms
64 bytes from fe80::fc54:ff:feba:c962%vnet2: icmp_seq=3 ttl=64 time=0.085 ms
^C
--- fe80::fc54:ff:feba:c962 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 57ms
rtt min/avg/max/mdev = 0.068/0.078/0.085/0.007 ms
[root@frontserver ~]# ping -6 fe80::fc54:ff:fe0d:a39a
PING fe80::fc54:ff:fe0d:a39a(fe80::fc54:ff:fe0d:a39a) 56 data bytes
64 bytes from fe80::fc54:ff:fe0d:a39a%vnet1: icmp_seq=1 ttl=64 time=0.061 ms
64 bytes from fe80::fc54:ff:fe0d:a39a%vnet1: icmp_seq=2 ttl=64 time=0.078 ms
64 bytes from fe80::fc54:ff:fe0d:a39a%vnet1: icmp_seq=3 ttl=64 time=0.078 ms
^C
--- fe80::fc54:ff:fe0d:a39a ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 16ms
rtt min/avg/max/mdev = 0.061/0.072/0.078/0.010 ms
[root@frontserver ~]# ping 192.168.21
PING 192.168.21 (192.168.0.21) 56(84) bytes of data.
64 bytes from 192.168.0.21: icmp_seq=1 ttl=64 time=0.564 ms
64 bytes from 192.168.0.21: icmp_seq=2 ttl=64 time=0.227 ms
64 bytes from 192.168.0.21: icmp_seq=3 ttl=64 time=0.246 ms
^C
--- 192.168.21 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 40ms
rtt min/avg/max/mdev = 0.227/0.345/0.564/0.156 ms
[root@frontserver ~]# ping 192.168.22
PING 192.168.22 (192.168.0.22) 56(84) bytes of data.
64 bytes from 192.168.0.22: icmp_seq=1 ttl=64 time=0.243 ms
64 bytes from 192.168.0.22: icmp_seq=2 ttl=64 time=0.388 ms
64 bytes from 192.168.0.22: icmp_seq=3 ttl=64 time=0.335 ms
^C
--- 192.168.22 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 31ms
rtt min/avg/max/mdev = 0.243/0.322/0.388/0.059 ms
[root@frontserver ~]#

So, I don't understand why virsh doesn't show any vnet#s or why ifconfig doesn't report ip4 addresses but does report ip6 addresses.

What I have now is:

Code: Select all

ens1<---->|
          |<->nm-team1<->nm-bridge1
wlp16s0<->|
Morgan Read

Post Reply

Return to “CentOS 8 - Networking Support”