Description of Problem: neat writes this configuration in ifcfg-eth0 for a DHCP interface: BOOTPROTO=DHCP which ifup handles okay, but ifdown bypasses the interface dropping sequence for DHCP interfaces and ends up leaving dhcpcd running. Essentially, the trap looks like this: if ["$BOOTPROTO" = bootp -o "$BOOTPROTO" = dhcp ]; then [ -n "`pidof -x dhcpcd`" ] && { dhcpcd -k ${DEVICE} retcode=$? ... you get the idea. Point is, when neat sets that BOOTPROTO=DHCP, it evades this trap and the interface is dropped rather messily, leaving dhcpcd still running. There is also one other error associated with this: Error: an inet prefix is expected rather than "/". I'm not sure where that is coming from, but it seems related, and it goes away when you manually fix the ifcfg-eth0 file. How Reproducible: Always Steps to Reproduce: 1. Configure a DHCP interface with neat. 2. Note the ifcfg-eth0 file has BOOTPROTO=DHCP 3. try to ifdown eth0, and notice the ipcalc errors and that dhcpcd is still running after the interface is brought down. Actual Results: ifdown spews errors and doesn't kill dhcpcd like it should Expected Results: clean interface shutdown, with dhcpcd terminated. Additional Information:
it shouldn't even work on ifup, AFAIK.
Will fix.
*** This bug has been marked as a duplicate of 50902 ***