New Network profile every reboot

Issues related to configuring your network
Post Reply
wiscojay
Posts: 5
Joined: 2020/06/02 13:02:38

New Network profile every reboot

Post by wiscojay » 2020/06/02 13:45:24

Browsing the forum, I found a similar issue here: viewtopic.php?f=56&t=74339. Unfortunately it is marked solved and didn't seem to answer my question. I just installed a fresh version CentOS Linux release 8.1.1911. I created a KVM of CentOS-7.6.1810 and wanted to create a bridge network for the KVM. I followed the steps for using the nmcli tool here: https://www.tecmint.com/create-network- ... -centos-8/. Everything worked perfectly except that on reboot (the whole machine not the KVM), the network didn't come back up. I figured I needed to persist the bridge in the network-scripts and so tried creating a bridge connection that following various web site instructions. At one point I had things so messed up that I just deleted all the network scripts in etc/sysconfig/network-scripts to start from a clean slate. The actual problem:

I have a profile, ifcfg-enp0s31f6 in etc/sysconfig/network-scripts. Every boot up it's not recognized and the network doesn't come up. If I go to settings, and physically choose to 'connect' the wired connection it is successfull however it creates a new network profile, ifcfg-enp0s31f6-1. This process goes on indefinantly...every reboot, when I choose to connect, Network Manager creates a new profile; ifcfg-enp0s31f6-1-1, -1-2, -1-3........

If I diff the network profiles, they are all Identical except the UUID. I turned tracing and debug on for network manager and had a look at journalctl -u NetworkManager. The only suspicions entery I see is this:
<warn> [1591101829.0355] ifcfg-rh: load[/etc/sysconfig/network-scripts/ifcfg-enp0s31f6]: failure to read file: Invalid GATEWAY IP4 address 'br1'

Which is very suspicious as the network script doesn't specify the GATEWAY at all.

So....Any have any Idea what is going on?

User avatar
TrevorH
Forum Moderator
Posts: 29942
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: New Network profile every reboot

Post by TrevorH » 2020/06/02 14:26:39

Is the MAC address as reported by ip link show the same on each boot?
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

wiscojay
Posts: 5
Joined: 2020/06/02 13:02:38

Re: New Network profile every reboot

Post by wiscojay » 2020/06/02 14:38:28

Hey thanks for the response. Yes, the mac address doesn't change on boot, only the UUID. I was going to post the contents of the network scripts files but didn't know if that was allowed (sorry, new here...)

User avatar
TrevorH
Forum Moderator
Posts: 29942
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: New Network profile every reboot

Post by TrevorH » 2020/06/02 14:40:31

Yes, it's allowed and encouraged to share any information that might assist in helping you. If you need to obscure any information in those files then please try to make sure that you don't obscure so much as to make them useless! You can wrap the contents of the file in [code][/code] tags so that the forum will format them correctly.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

wiscojay
Posts: 5
Joined: 2020/06/02 13:02:38

Re: New Network profile every reboot

Post by wiscojay » 2020/06/02 15:07:47

ok, so i just performed a reboot, and as I described the network did not immediately come up:

Code: Select all

 nmcli
virbr0: connected to virbr0
        "virbr0"
        bridge, 52:54:00:8A:0A:FF, sw, mtu 1500
        inet4 192.168.122.1/24
        route4 192.168.122.0/24

enp0s31f6: disconnected
        "Intel Ethernet"
        ethernet (e1000e), D4:81:D7:7B:CF:8A, hw, mtu 1500

wlp2s0: unavailable
        "Intel 8260"
        wifi (iwlwifi), 26:BC:22:80:81:8E, hw, mtu 1500

lo: unmanaged
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

virbr0-nic: unmanaged
        "virbr0-nic"
        tun, 52:54:00:8A:0A:FF, sw, mtu 1500
Here are the contents of /etc/sysconfig/network-scripts/
$ ls
ifcfg-enp0s31f6 ifcfg-enp0s31f6-1
notice: ifcfg-enp0s31f6 is my original profile script that doesn't get recognized on startup. the '-1' was the profile created on my last boot up. If I now navigate to the network settings and select to 'connect' connect the wired connection the network comes up:

Code: Select all

nmcli
enp0s31f6: connected to Wired connection 1
        "Intel Ethernet"
        ethernet (e1000e), D4:81:D7:7B:CF:8A, hw, mtu 1500
        ip4 default
        inet4 192.168.254.21/24
        route4 0.0.0.0/0
        route4 192.168.254.0/24
        inet6 fe80::a370:f5a9:fcbd:6155/64
        route6 fe80::/64
        route6 ff00::/8
However, I now have yet another profile script:

Code: Select all

ls
ifcfg-enp0s31f6  ifcfg-enp0s31f6-1  ifcfg-Wired_connection_1
here are the contents of the original profile enp0s31f6:

Code: Select all

TYPE=Ethernet
BOOTPROTO=dhcp
PROXY_METHOD=none
BROWSER_ONLY=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
DEVICE=enp0s31f6
NAME="enp0s31f6"
ONBOOT=yes
HDWADDR=d4:81:d7:7b:cf:8a
contents of newly created profile by NetworkManager ifcfg-Wired_connection_1:

Code: Select all

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME="Wired connection 1"
UUID=4eb60479-cab8-485f-b053-48abecc7c8ea
DEVICE=enp0s31f6
ONBOOT=yes

User avatar
TrevorH
Forum Moderator
Posts: 29942
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: New Network profile every reboot

Post by TrevorH » 2020/06/02 15:17:54

From a quick read, the only thing I notice is that your original file does not have a UUID line in it at all. Perhaps try transplanting the one from the new file to it?
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

wiscojay
Posts: 5
Joined: 2020/06/02 13:02:38

Re: New Network profile every reboot

Post by wiscojay » 2020/06/02 16:07:41

TrevorH wrote:
2020/06/02 15:17:54
From a quick read, the only thing I notice is that your original file does not have a UUID line in it at all. Perhaps try transplanting the one from the new file to it?
Perhaps this is a different conversation, but I did not think it was necessary to 'bind' UUID or HDWADDR in the network scripts. I have an embedded linux system I tinker with running centos7. I clone the OS and create a USB installer I can use to install it to identical but separate systems. The network profile script for this only specifies a DEVICE and a NAME, which works to bring up the network every time.

None the less, I tried your suggestion with no success. I added the UUID to the original ifcfg-enp0s31f6 and rebooted, but I went through the same procedure with getting yet another network profile.

Code: Select all

$ ls
ifcfg-enp0s31f6  ifcfg-enp0s31f6-1  ifcfg-Wired_connection_1  ifcfg-Wired_connection_1-1

Code: Select all

$ cat ifcfg-Wired_connection_1-1
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME="Wired connection 1"
UUID=476fe2de-ddf7-44e7-8be0-44f3996a1212
DEVICE=enp0s31f6
ONBOOT=yes
original with updated UUID:

Code: Select all

$ cat ifcfg-enp0s31f6
TYPE=Ethernet
BOOTPROTO=dhcp
PROXY_METHOD=none
BROWSER_ONLY=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
DEVICE=enp0s31f6
NAME="enp0s31f6"
ONBOOT=yes
HDWADDR=d4:81:d7:7b:cf:8a
UUID=4eb60479-cab8-485f-b053-48abecc7c8ea

User avatar
TrevorH
Forum Moderator
Posts: 29942
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: New Network profile every reboot

Post by TrevorH » 2020/06/02 16:25:18

You should probably remove all the duplicates as I suspect it might get quite cross if it comes across duplicate UUIDs.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

wiscojay
Posts: 5
Joined: 2020/06/02 13:02:38

Re: New Network profile every reboot

Post by wiscojay » 2020/06/02 19:06:21

sorry, still no luck even removing the duplicates. executing journalctl -u NetworkManager is too large to attach here, is there anything else I could provide?

User avatar
TrevorH
Forum Moderator
Posts: 29942
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: New Network profile every reboot

Post by TrevorH » 2020/06/02 21:16:14

I've got no idea what's going on, sorry.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

Post Reply

Return to “CentOS 8 - Networking Support”