Okay community, let's see if we can figure this one out, cause I'm out of answers.

Where I work I am setting up a bunch of RedHat Enterprise Linux servers. There is a collection of RHEL6 and RHEL7 servers.

On the RHEL6 servers, I am using the standard network configuration tool by configuring it in /etc/sysconfig/network-scripts/ifcfg-eth0 and a dhclient configuration file in /etc/dhclient-eth0.conf. Everything works properly, I am assigned the custom FQDN by our DNS servers (e.g. hostname.ad.company.tld) and when the DHCP lease is up, it is renewed automatically.

Here is the issue:

In RHEL7, NetworkManager is enabled by default. On our Kickstart, I have removed NetworkManager and went back to configuring network and dhcp the way it is done in RHEL6. All of the configuration is the same (sans using /etc/sysconfig/network-scripts/ifcfg-ens192 instead of eth0) and works fine for the first DHCP lease.

Once the lease is up, it seemingly doesn't renew it until I issue a systemctl restart network command.

I have looked and looked and I am coming up short. There must be something different in RHEL7 or something not configured when you disable NetworkManager, but I cannot for the life of me figure it out.

Anyone have any thoughts?

As I know these usually help, I'll post my RHEL7 configuration files, and the snippet from the logs where it loses the DHCP lease.


# Generated by dracut initrd


send host-name "hostname";
send fqdn.fqdn "hostname.ad.company.tld";
send fqdn.server-update off;


Jun 27 23:06:09 sa-kbwiki01 avahi-daemon[591]: Withdrawing address record for on ens192.
Jun 27 23:06:09 sa-kbwiki01 avahi-daemon[591]: Leaving mDNS multicast group on interface ens192.IPv4 with address xxx.xx.xx.xxx.
Jun 27 23:06:09 sa-kbwiki01 avahi-daemon[591]: Interface ens192.IPv4 no longer relevant for mDNS.
  • That log snippet doesn't show your DHCP lease being lost. Keep looking, there should be other more relevant entries. Jul 2, 2014 at 15:24
  • From what I recall hearing pre-launch is that networkManager is not the same PoS it was years ago and Red Hat more or less forces you to learn to live with it. Having said that, the documentation mentions that NetworkManager has been made responsible for starting dhclient, so it could be that without NM, dhclient is run with the -1 option and doesn't become a daemon.
    – HBruijn
    Jul 2, 2014 at 15:36
  • @MichaelHampton I do not see anything else in /var/log/messages. Other things that use the network are operating fine until that line, at which point everything starts saying no network available.
    – cjmaio
    Jul 2, 2014 at 15:59
  • @HBruijn That gives me somewhere to start... though when doing a ps aux | grep dhclient I do see that the -1 flag is being set... is there anywhere else that dhclient would log to other than /var/log/messages?
    – cjmaio
    Jul 2, 2014 at 16:00
  • Yeah, NM is fairly safe to use these days unless you have a very complicated setup. I do wonder why you're running Avahi though. Jul 2, 2014 at 16:01

2 Answers 2


I ended up figuring out the issue.

There is a flag you can set in your kickstart file, biosdevname=0, which is supposedly supposed to revert RHEL7 into using the old ethernet naming standard, e.g. eth0

It didn't do that, seemed to have no effect. I thought I had removed it, but I guess not.

It must have told the installer to setup things incorrectly. When I removed that from the kickstart, and built the machine again, I no longer had the issue of dhclient dying.

  • 1
    It also has to be added to your kernel command line in your grub configuration. I don't know if anaconda does this for you. Jul 30, 2014 at 22:00

To revert to regular interface names, it's as simple as

sed -i '
  /CMDLINE/s/ /net.ifnames=0/
  ' /etc/default/grub
grub2-mkconfig -o /boot/grub2/grub.cfg
init 6

Don't look at the /etc/grub tree, though: it's now been made horrendously complicated so it's a risky toxic mess like systemd.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .