On 2020-02-11 00:09, Nicolas Kovacs wrote:
Le 10/02/2020 à 16:12, Leroy Tennison a écrit :
There may be ways to force NIC naming, I've done so but only on Ubuntu so
you'll need to do the research if it's important to you. Things to look for
based on my experience: 70-persistent-net.rules,
Le 10/02/2020 à 16:12, Leroy Tennison a écrit :
There may be ways to force NIC naming, I've done so but only on Ubuntu so
you'll need to do the research if it's important to you. Things to look for
based on my experience: 70-persistent-net.rules, net.ifnames=0,
biosdevname=0.
That's exactly
On Mon, Feb 10, 2020 at 03:12:11PM +, Leroy Tennison wrote:
> There may be ways to force NIC naming, I've done so but only on Ubuntu so
> you'll need to do the research if it's important to you. Things to look for
> based on my experience: 70-persistent-net.rules, net.ifnames=0,
of Nicolas Kovacs
Sent: Sunday, February 9, 2020 12:51 PM
To: centos@centos.org
Subject: [EXTERNAL] Re: [CentOS] CentOS 7 : network interface renamed from eth0
to eth1 after reboot
Le 09/02/2020 à 16:54, Alexander Dalloz a écrit :
> "Kernel always uses the ethX naming convention at b
On Sun, 9 Feb 2020 at 13:51, Nicolas Kovacs wrote:
> Le 09/02/2020 à 16:54, Alexander Dalloz a écrit :
> > "Kernel always uses the ethX naming convention at boot when it
> enumerates
> > network devices. Due to parallelization, the order of the kernel
> interface
> > enumeration is expected to
Le 09/02/2020 à 16:54, Alexander Dalloz a écrit :
"Kernel always uses the ethX naming convention at boot when it enumerates
network devices. Due to parallelization, the order of the kernel interface
enumeration is expected to vary across reboots."
Thanks for the heads up.
I experimented
Am 09.02.2020 um 16:14 schrieb Nicolas Kovacs:
Le 09/02/2020 à 14:10, Nicolas Kovacs a écrit :
Any suggestions ?
I forgot to add. The onboard NIC is a Broadcom card.
$ lspci | grep -i net
02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8100/8101L/8139 PCI Fast Ethernet
Le 09/02/2020 à 14:10, Nicolas Kovacs a écrit :
Any suggestions ?
I forgot to add. The onboard NIC is a Broadcom card.
$ lspci | grep -i net
02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
02:09.0 Ethernet controller:
Le 09/02/2020 à 15:15, Günther J. Niederwimmer a écrit :
this is coming from The NetworkManager?
I set in my config *-eth0 the HWADDR=
and NM_CONTROLLED=no
I forgot to add : I removed NetworkManager as I do on all my servers.
--
Microlinux - Solutions informatiques durables
7,
Hello,
Am Sonntag, 9. Februar 2020, 14:10:44 CET schrieb Nicolas Kovacs:
> Hi,
>
> I've done my fair share of CentOS 7 installations, but this is the first
> time I have this kind of weird problem. Here goes.
>
> In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm
> using
Le 09/02/2020 à 14:52, Salim Shaw a écrit :
Very strange and as you suggested delete the ifcfg-eth0 file and recreate,
specify your settings. I suspect your wireless device and or systemboard is
faulty. Is there a BIOS hardware self-test you could perform to check the
integrity of your hardware?
Very strange and as you suggested delete the ifcfg-eth0 file and recreate,
specify your settings. I suspect your wireless device and or systemboard is
faulty. Is there a BIOS hardware self-test you could perform to check the
integrity of your hardware?
On Sun, Feb 9, 2020, at 8:10 AM, Nicolas
Hi,
I've done my fair share of CentOS 7 installations, but this is the first time I
have this kind of weird problem. Here goes.
In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm
using as a bare metal sandbox server for testing purposes.
The CentOS 7 installer sees
13 matches
Mail list logo