similar to: NICs order

On 02/01/2016 07:00 AM, Leroy Tennison wrote: > The issue here may be systemd ... > Web documentation at freedesktop.org says net.ifnames needs to be set to zero, I found just the opposite but if it doesn't work for you try both before giving up. Just to clarify: net.ifnames=0 disables the systemd/udev interface renaming feature. biosdevname=0 disables the biosdevname interface

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,

The issue here may be systemd (I've seen/agree with the venting, this is another example). If you're getting non-eth names there's a program called biosdevname which may be deciding how to name NICs for you. If that's the case then then the <nn>-net.rules may be ineffective unless the following is added as kernel command line parameters: net.ifnames=1 and biosdevname=0 I

El Lunes 01/02/2016, Daniel Ruiz Molina escribi?: > Hi, > > After installing CentOS 7 in a server with 2 NICs, system detects eth0 > and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as > eth1. I have forced HWADDR attribute in > /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but after rebooting, > order is the same... > > How can I solve it? >

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 am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --ondisk=sda

Once upon a time, Leroy Tennison <leroy at datavoiceint.com> said: > The executable could be placed on mounted read-only media That's not as secure as you think. Linux bind mounts can mount a file over another file (plus there's overlay filesystems), so it's possible to replace a binary even on a read-only device. -- Chris Adams <linux at cmadams.net>

You think this is irritating, what about when you're trying to replicate the network configuration to failover hardware... There is a way around this, I haven't tried it on CentOS but on Ubuntu there are kernel command line parameters: net.ifnames=1 biosdevname=0 which will override this behavior. Again, on Ubuntu these are added in /etc/default/grub as parameters to

The device I encountered it on had 10 NICS, at installation 6 of them got the new naming convention and four of them got the eth convention. I guess my question is "what's wrong with using the MAC address?" Yes, I know some things don't have MAC addresses, let the exceptional situation be the exception. ----- Original Message ----- From: "Jonathan Billings"

On Thu, Feb 28, 2019 at 01:32:12AM -0800, si-wei liu wrote: > > > Will the > > > change break userspace further? > > > > > > -Siwei > > Didn't you show userspace is already broken. You can't "further > > break it", rename already fails. > It's a race, userspace tends to give slave a user(space) desired name but >

Thanks Robert, I was doing that but it was still renaming to ens*. However, I now know why, and have fixed it. For those who are interested, the problem was that when I created the base image from a kickstart I didn't pass net.ifnames=0 to virt-create, and I ended up with an image that had forgotten about eth0 completely. I have now redone the kickstart with net.ifnames=0 and all is well.

I've several USB <-> RS-232 dongles around. As well as a few embedded devices. They all "Just Work (tm)" on Redhat, CentOS, Fedora, Debian, Raspian and Kali. Knock on wood - never had a problem using any of them. As the drivers are part of the kernel, I'd expect any distro using a recent kernel to do well. On Wed, Jul 8, 2020 at 9:24 AM Leroy Tennison <leroy at

On 2019-11-18 12:45, Stephen John Smoogen wrote: > On Mon, 18 Nov 2019 at 13:22, Jerry Geis <jerry.geis at gmail.com> wrote: >> >> I am trying to boot a grub entry for CentOS 8 >> >> menuentry "Server Install CentOS 8" { >> linux /boot/vmlinuz noverifyssl ks= >>

Hi For years (long time) I had " net.ifnames=0 biosdevname=0 " and it worked as it should (6.X, 7.X) I never had any problems, until yesterday. I started upgrading my machines and I stopped after the first one showed issues and I will not update all the other ones until this is sorted. I have problems keeping the interfaces in order as I wanted them to be assigned to eth0, eth1 ..

On Dec 10, 2015, at 6:05 PM, Leroy Tennison <leroy at datavoiceint.com> wrote: > There is a freedesktop.org web page about why they did this - it has to do with mobile devices and plug-and-play networking. Take that page's statement about setting net.ifnames=0 cautiously, I found it was the exact opposite. To be honest, I found that this change better suited servers, which often

On Thu, Feb 28, 2019 at 05:30:56PM -0800, si-wei liu wrote: > > > On 2/28/2019 6:26 AM, Michael S. Tsirkin wrote: > > On Thu, Feb 28, 2019 at 01:32:12AM -0800, si-wei liu wrote: > > > > > Will the > > > > > change break userspace further? > > > > > > > > > > -Siwei > > > > Didn't you show userspace is

On Mon, 18 Nov 2019 at 13:22, Jerry Geis <jerry.geis at gmail.com> wrote: > > I am trying to boot a grub entry for CentOS 8 > > menuentry "Server Install CentOS 8" { > linux /boot/vmlinuz noverifyssl ks= > https://devgeis.LayeredSolutionsInc.com:443/kickstart/ks_update_to_server8.cfg > biosdevname=0 net.ifnames=0 ksdevice=eth0 ip=192.168.1.13 >

<sigh> Thanks - I'll keep that in mind... ________________________________ From: CentOS <centos-bounces at centos.org> on behalf of Chris Adams <linux at cmadams.net> Sent: Thursday, November 14, 2019 10:57 AM To: centos at centos.org <centos at centos.org> Subject: [EXTERNAL] Re: [CentOS] how to know when a system is compromised Once upon a time, Leroy Tennison

I have built a CentOS 8 base image from a kickstart, for use in OpenStack. This image boots fine but the problem I have is that I can't stop udev from renaming the network device from eth0 to ens<something>. I have /etc/sysconfig/network-scripts/ifcfg-eth0 with the correct HWADDR defined in it, and have set net.ifnames=0 and biosdevname=0 in the grub configuration, but nothing I have

I installed 7.1 with the command line values biosdevname=0 net.ifnames=0 thinking this would result in ifcfg-eth0 being the file to use... The system still created an ifcfg-eno1 file and that was what is being used for network config information. I remove the ifcfg-eno1 and rebooted - got no network. I then copied back the ifcfg-eth0 to ifcfg-en01 and changed the device name in the file and