Cockpit - Network schizophrenia

Issues related to configuring your network
Post Reply
User avatar
penguinpages
Posts: 67
Joined: 2015/07/21 13:58:05

Cockpit - Network schizophrenia

Post by penguinpages » 2020/09/10 16:28:20

Really confused here with CentOS8 networking.

I did a fresh minimal installation. Three node cluster based on CentOS8 for small HCI cluster.

When I setup network on initial load I just bound IP to the mgmt interface. Loaded up Cockpit and tried to give it a try to setup the rest.
cockpit nic setup
cockpit nic setup
medusa_diagram.png (78.57 KiB) Viewed 135 times
What I am seeing is complete bedlam on the network. I can't figure out where it is pulling its configuration from.

After above is setup.. and working. All I do is reboot and this is the configuration post reboot:
#######
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
valid_lft forever preferred_lft forever
2: enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 00:e0:4c:b7:43:4f brd ff:ff:ff:ff:ff:ff
inet 172.16.100.103/24 brd 172.16.100.255 scope global noprefixroute enp7s0
valid_lft forever preferred_lft forever
3: enp3s0f0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0f:53:09:01:94 brd ff:ff:ff:ff:ff:ff
inet6 fe80::20f:53ff:fe09:194/64 scope link
valid_lft forever preferred_lft forever
4: enp0s29u1u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:10:60:31:ee:07 brd ff:ff:ff:ff:ff:ff
5: enp3s0f1np1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:0f:53:09:01:95 brd ff:ff:ff:ff:ff:ff
inet 172.16.101.103/24 brd 172.16.101.255 scope global noprefixroute enp3s0f1np1
valid_lft forever preferred_lft forever
6: bridge101: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:e0:4c:b7:43:4f brd ff:ff:ff:ff:ff:ff
inet6 fe80::847e:c1ff:fe30:e91d/64 scope link
valid_lft forever preferred_lft forever
7: bridge100: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:e0:4c:b7:43:4f brd ff:ff:ff:ff:ff:ff
inet6 fe80::6854:3fff:fec6:93fe/64 scope link
valid_lft forever preferred_lft forever
8: enp7s0.100@enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master bridge100 state LOWERLAYERDOWN group default qlen 1000
link/ether 00:e0:4c:b7:43:4f brd ff:ff:ff:ff:ff:ff
9: bridge102: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:e0:4c:b7:43:4f brd ff:ff:ff:ff:ff:ff
inet6 fe80::d48a:82ff:fed2:38e0/64 scope link
valid_lft forever preferred_lft forever
10: enp7s0.102@enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master bridge102 state LOWERLAYERDOWN group default qlen 1000
link/ether 00:e0:4c:b7:43:4f brd ff:ff:ff:ff:ff:ff
11: enp7s0.101@enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master bridge101 state LOWERLAYERDOWN group default qlen 1000
link/ether 00:e0:4c:b7:43:4f brd ff:ff:ff:ff:ff:ff
12: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:7a:96:37 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
13: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
link/ether 52:54:00:7a:96:37 brd ff:ff:ff:ff:ff:ff


#####

Going into /etc/sysconfig/networking and reviewing it makes my head hurt even more... (see attached files).... as it matches what cockpit is showing...

So ... what the heck is going on here. is NetworkManager some how pulling from some different save location?
Attachments
ifcfg-bridge101.txt
(173 Bytes) Downloaded 2 times
ifcfg-bridge100.txt
(173 Bytes) Downloaded 2 times

User avatar
penguinpages
Posts: 67
Joined: 2015/07/21 13:58:05

Re: Cockpit - Network schizophrenia

Post by penguinpages » 2020/09/10 18:09:42

Ok.. trying to learn more nmcli... and poked around and saw this weirdness.

############
NAME UUID TYPE DEVICE
enp0s29u1u4 72936846-cd68-41b7-892b-8059c708ca89 ethernet enp7s0
bridge100 c057d30c-bc88-4413-b34a-530019a3b2d6 bridge bridge100
bridge101 bdeb1f60-4f3d-42a5-88f0-5bcfb4378785 bridge bridge101
bridge102 f0cef37e-302a-44f0-a8f5-eae7d9c746e5 bridge bridge102
enp3s0f0np0 bd7f729c-6c50-45aa-bac9-48439220a33f ethernet enp3s0f0np0
enp7s0.100 c0e742ec-660a-4f11-8b0c-c769adf5d925 vlan enp7s0.100
enp7s0.101 afc0f6ba-d442-42c3-ab35-cef0b6e773f6 vlan enp7s0.101
enp7s0.102 734232a5-61ac-4887-a722-7fa8c4515c2a vlan enp7s0.102
enp7s0 818213d2-09ae-4434-b05d-8f944f709a28 ethernet --
##########

I double checked /etc/sysconfig/network/ scripts to make sure each had a unique UUID and their was not some kind of weird duplication... they did not.

I just decided to give up on nmtui and simple setup and wipe out all configuration files in /etc/sysconfig/network... reboot.. and with that base.. rebuild


# Setup mgmt nic
nmcli con add type ethernet con-name enp0s29u1u4 ifname enp0s29u1u4 ip4 172.16.100.103/24 gw4 172.16.100.1
nmcli con add type ethernet con-name enp3s0f0np0 ifname enp3s0f0np0 ip4 172.16.101.103/24

# Then use cockpit to setup rest
medusa_net_v2_diagram.png
medusa_net_v2_diagram.png (35.79 KiB) Viewed 119 times

<reboot>

configuration held.


I did this once before I opened this ticket.. but last time I used nmtui vs nmcli.... you have to add the nic and just used adapter name... maybe later I will test this as the root cause.. but will post as I learn more about what it got confused or if this is a nmcli bug.

User avatar
penguinpages
Posts: 67
Joined: 2015/07/21 13:58:05

Re: Cockpit - Network schizophrenia

Post by penguinpages » 2020/09/13 17:52:23

I did confirm this in so much that two reloads.. Fresh.. double check settings. Post reboot.. settings shifted to incorrect interfaces.

as to root cause ... TBD.. I will post if i find out more.

Post Reply

Return to “CentOS 8 - Networking Support”