similar to: CentOS 7 : network interface renamed from eth0 to eth1 after reboot

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 Kovacs wrote: > Hi, > > I've done my fair share of CentOS 7 installations, but this is the

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 Adapter (rev 10) > 02:09.0 Ethernet controller: Broadcom Inc.

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. ________________________________ From: CentOS <centos-bounces at centos.org> on behalf of Nicolas Kovacs <info at microlinux.fr> Sent: Sunday,

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: Broadcom Inc. and subsidiaries BCM4401-B0 100Base-TX (rev 02) This card gets randomly renamed to either

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 as a bare metal sandbox server for testing purposes. > > The

Hi, I'm running CentOS on all kinds of setups: servers, workstations, desktops and laptops. Up until now, I'm only using NetworkManager on laptops, since it makes sense to use it there. On servers and desktop clients, I usually remove it and configure the network "traditionally" by simply editing /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf, /etc/hosts,

Hi, I often have to deal with relatively obsolete hardware in schools, public libraries, small town halls, etc. I still have a handful of CentOS 5.x installations around for these, but I wonder what CentOS 6.x desktop specs are, e. g. the minimum requirements (in terms of CPU and RAM) to reasonably run it. Will a battered first-generation P-IV with 512 MB RAM be sufficient? How much RAM does

Hi, I'm just migrating some stuff from Slackware Linux to CentOS, and I have a question about the orthodox way of configuring a network connection. On a desktop or workstation, I usually get rid of NetworkManager: # systemctl stop NetworkManager # yum remove NetworkManager Then I edit the /etc/sysconfig/network-scripts/ifcfg-XXXXX file corresponding to my network interface. Here's

Le 18/02/2020 ? 12:28, Anand Buddhdev a ?crit?: > Neither. The DNS configuration should not normally be bound to a > specific interface, so don't configure it with any interface. If you do, > and that interface goes down, your DNS config also disappears. I would like to do that very much, only NetworkManager makes you jump through burning loops to do so. With network-scripts, it

Hi, I have a few identical Dell Optiplex 7010 machines that I want to use for our school's computer room. I tried to clone these installations (like I did before on CentOS 5 and various versions of Slackware), but this time I ran into a problem. Here's what I did. 1. Install one computer and zero unused hard disk sectors with dd. 2. Send the image to a local FTP server using G4L

Hi, I have a LAN server running CentOS 5.11 with two NICs eth0 and eth1. I'd like to swap the interface names, but I don't know how to go about that under CentOS. Here's what I would do on a Slackware server (I have one next to me in my office). Open /etc/udev/rules.d/70-persistent-net.rules and edit it: # PCI device 0x8086:/sys/devices/pci0000:00/0000:00:04.0/0000:03:00.0 (e1000e)

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 quite a bit, and found some surprising behavior. So I documented everything in a

Hi Everyone: I installed CentOS 4.4 on a new Dell 2950 using the server cd. No errors during the installation and no errors on bootup when loading the Eth0 or Eth1 interfaces. I currently have iptables stopped and selinux disabled. The interfaces have been given a static ip (192.168.1.x). the subnet is 255.255.255.0 and the gateway is 192.168.1.1. I can not ping any device on my network

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 the solution I described in detail in my blog article. :o) --

I''ve been using Puppet now for a month or so and I''ve come to a problem that may warrant an additional Puppet metaparameter. I''m advocating the addition of a metaparameter called "preaction" (or something like that), which will perform some arbitrary action before the resource is modified. There may be a way to do this within Puppet already (with some

Hi, I'm running CentOS 7 on all my servers, in three different contexts : 1. simple local server 2. public facing server 3. router/gateway/firewall I'm currently in the process of moving my KISS-style network-scripts-style configurations to something more orthodox based on NetworkManager. Scenarios (1) and (2) caused no problems, but (3) is giving me some headache. Let me

Hi, A couple months ago, I migrated our local school (two servers, 20 desktop clients) from Slackware 14.1 to CentOS 7. The desktop clients are running a customized lightweight desktop based on Xfce: https://blog.microlinux.fr/poste-de-travail-xfce-centos-7/ Home directories are all on the server, and authentication is centralized. Everything works fine so far. With Slackware I had found a

Hello, I created a CentOS 5.0 x86_64 guest under Debian Etch with Xen 3.0.3 and it boots fine except for one re-occuring problem - whenever it boots the /etc/sysconfig/network-scripts/ifcfg-eth0 script gets renamed to .bak and doesn''t configure the ethernet device. Here is the content of this file: TYPE=Ethernet DEVICE=eth0 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.0.247

Le 17/11/2019 ? 14:15, Jonathan Billings a ?crit?: > I?m curious why you list these as ?cruft? packages? > > chrony > firewalld > iperf > NetworkManager-libnm * chrony: I'm using ntpd and ntpdate * firewalld: https://github.com/kikinovak/firewall * iperf: replaced by iperf3 * NetworkManager: great on laptops, useless on servers > > Also, I?m sure it?s helpful for

Dear All, I''m trying to configure Xen on a laptop with a BCM4401 ethernet board The Debian xen kerner 2.6.18-5 is not handling wlll that board I get the follwing in messages b44: Probe failed with error -5 Any help is welcome Regards Maurice _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users