Bug 50771 - neat writes the BOOTPROTO setting in all caps, which breaks ifdown on a DHCP interface.
Summary: neat writes the BOOTPROTO setting in all caps, which breaks ifdown on a DHCP ...
Status: CLOSED DUPLICATE of bug 50902
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-02 23:16 UTC by Panic
Modified: 2008-05-01 15:38 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-08-03 15:01:09 UTC


Attachments (Terms of Use)

Description Panic 2001-08-02 23:16:48 UTC
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:

Comment 1 Bill Nottingham 2001-08-03 02:58:51 UTC
it shouldn't even work on ifup, AFAIK.

Comment 2 Trond Eivind Glomsrxd 2001-08-03 15:01:05 UTC
Will fix.

Comment 3 Trond Eivind Glomsrxd 2001-08-05 19:50:58 UTC

*** This bug has been marked as a duplicate of 50902 ***


Note You need to log in before you can comment on or make changes to this bug.