#779681 executing ifdown on a dhcp configured interface unconfigures other dhcp interfaces

Package:
ifupdown
Source:
ifupdown
Description:
high level tools to configure network interfaces
Submitter:
"David S. Roth"
Date:
2015-07-07 15:24:12 UTC
Severity:
normal
#779681#5
Date:
2015-03-03 23:43:44 UTC
From:
To:
The system under test has 3 network interfaces each configured using dhcp.

System configuration:

/etc/network/interfaces:

auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

auto eth2
allow-hotplug eth2
iface eth2 inet dhcp

auto eth3
allow-hotplug eth3
iface eth3 inet dhcp

/etc/dhcp/dhclient.conf:

option rfc3442-classless-static-routes code 121 = array of unsigned
integer 8;

#send host-name "andare.fugue.com";
send host-name = gethostname();

interface "eth2" {
     request subnet-mask, broadcast-address, time-offset, interface-mtu,
ntp-servers,
     domain-name-servers, domain-name;
     require domain-name-servers, domain-name;
     send dhcp-client-identifier "cs-controller1";}


interface "eth3" {
     request subnet-mask, broadcast-address, time-offset, interface-mtu,
ntp-servers,
     domain-name-servers, domain-name;
     require domain-name-servers, domain-name;
     send dhcp-client-identifier "cs-controller2";}


Post boot 'ifdown ethN; ifup ethN' is executed to reconfigure the dhcp
interfaces one at a time.

Executing ifdown on a specific interface unconfigures the other dhcp
interfaces rather than just the targeted interface.

E. g.: 'ifdown eth2' results in eth3 being unconfigured.

When executing ifdown eth2 we would expect only eth2 to be affected.

#779681#10
Date:
2015-07-07 15:13:59 UTC
From:
To:
I can confirm that this bug affects also version 0.7.54.

Christoph