Debian Bug report logs - #314819
ifupdown: ifup fails to bring up eth0 interface with correct ip address

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Alan Chandler <alan@chandlerfamily.org.uk>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ifupdown: ifup fails to bring up eth0 interface with correct ip address

Date: Sat, 18 Jun 2005 19:04:28 +0100

Package: ifupdown
Version: 0.6.7
Severity: important


Something has changed in ifupdown recently that means that it will not
bring up my eth0 interface

If I stop networking and try and bring up the interface it fails

/etc/init.d/networking stop
ifup -a

when /etc/network/interfaces has the following

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp


fails with the following output

root@kanger ~ # /etc/init.d/networking stop
Deconfiguring network interfaces...done.
root@kanger ~ # ifup -a
ifup: interface lo already configured
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:50:da:cf:a5:06
Sending on   LPF/eth0/00:50:da:cf:a5:06
Sending on   Socket/fallback/fallback-net
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.20
SIOCADDRT: File exists
bound to 192.168.0.21 -- renewal in 10800 seconds.
RTNETLINK answers: Cannot assign requested address
root@kanger ~ #

ifconfig reveals that the internet address has been set to a default value


roott@kanger ~ # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:50:DA:CF:A5:06
          inet addr:169.254.50.3  Bcast:0.0.0.0  Mask:255.255.0.0
          inet6 addr: fe80::250:daff:fecf:a506/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:285925 errors:0 dropped:0 overruns:0 frame:0
          TX packets:167574 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:333055717 (317.6 MiB)  TX bytes:13148490 (12.5 MiB)
          Interrupt:5 Base address:0xd400

root@kanger ~ #    

On the other hand - if I do

/etc/init.d/networking stop
dhclient eth0

the interface is brought up perfectly - thus

root@kanger ~ # /etc/init.d/networking stop
Deconfiguring network interfaces...done.
root@kanger ~ # dhclient eth0
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:50:da:cf:a5:06
Sending on   LPF/eth0/00:50:da:cf:a5:06
Sending on   Socket/fallback/fallback-net
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.20
SIOCSIFADDR: File exists
bound to 192.168.0.21 -- renewal in 10800 seconds.
root@kanger ~ # ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:50:DA:CF:A5:06
          inet addr:192.168.0.21  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::250:daff:fecf:a506/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:285969 errors:0 dropped:0 overruns:0 frame:0
          TX packets:167591 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:333061594 (317.6 MiB)  TX bytes:13149982 (12.5 MiB)
          Interrupt:5 Base address:0xd400

root@kanger ~ #  






-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-k7
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages ifupdown depends on:
ii  debconf [debconf-2.0]       1.4.51       Debian configuration management sy
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  net-tools                   1.60-13      The NET-3 networking toolkit

ifupdown recommends no packages.

-- debconf information:
  ifupdown/convert-interfaces: true

Message #10 received at 314819@bugs.debian.org (full text, mbox, reply):

From: Alan Chandler <alan@chandlerfamily.org.uk>

To: 314819@bugs.debian.org

Subject: Problem solved

Date: Mon, 11 Jul 2005 19:39:23 +0100

This appears to have been caused by package Zeroconf.  Remove package and 
problem goes away.

Strange thing - I never remember installing Zeroconf in the first place, and 
the description of it implies that it was not something I would want to 
install.
-- 
Alan Chandler
http://www.chandlerfamily.org.uk

Message #15 received at 314819@bugs.debian.org (full text, mbox, reply):

From: Cesare Leonardi <celeonar@tiscali.it>

To: 314819@bugs.debian.org, 348703@bugs.debian.org, 348729@bugs.debian.org, 351540@bugs.debian.org

Subject: Zeroconf breaks network configuration

Date: Sat, 11 Feb 2006 22:10:07 +0100

Today i have fallen in the these bug caused by zeroconf an i want to
contribute with information to confirm them and hoping to be useful to 
solve them.

Also for me zeroconf was not installed on my choice but as a recommended
package. This package was present on my system since some week but its
effects was clear to me only today, when i've tryed a new ADSL router:
trying to understand why i could not connect to internet, ifconfig
revelead me the presence of a 169.254.0.0/16 network address, that i
had never set. And working with the ifup/ifdown/ifconfig programs
brought me to strange behaviours.
Up to yesterday i haven't got connection troubles since i was using an 
ADSL modem with PPPoE, and seems it was unaffected.

The first thing that i have to report, and that i found to be related to
zeroconf, is that the boot process hang for some seconds during the eth0
bring up phase.
This delay is present even using ifup by hand.

After the boot process has completed, ifconfig reveal that eth0 has not
the network address i have set but another one that seems to be randomly
applied (and when i searched for information about such zeroconf thing,
i found that it was true).
The network address that i have set in /etc/network/interface file (say
192.168.1.1) it is not visible, but it is present in the system. In fact 
if i ping 192.168.1.1, it replies me.

Now if i try to bring down eth0, it seems to success, but if try to
bring it up again it says:

-------------------------------------------------------------------
# ifup eth0
SIOCSIFADDR: File exists
Failed to bring up eth0.
#
-------------------------------------------------------------------

In fact, now ifconfig surprisingly reveal:
-------------------------------------------------------------------
# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:01:4A:07:4C:1A
          inet addr:192.168.1.1  Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::201:4aff:fe07:4c1a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1386 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1289 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1140907 (1.0 MiB)  TX bytes:152146 (148.5 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

#
-------------------------------------------------------------------

My IP address is here but i can't  bring it down with ifdown because it
correctly says:

-------------------------------------------------------------------
# ifdown eth0
ifdown: interface eth0 not configured
#
-------------------------------------------------------------------

I have to thank those who have reported these bugs since has pointed me
that the cause of such caos was zeroconf. Before that i was lost in the
dark, since i really couldn't understand what was happening.

For now i have uninstalled zeroconf, since i don't need it and now i
don't want to learn how can it be useful to me. But i hope that the
package maintainer will found a solution that make the package default
settings do not conflict with existing configuration. And if it is not
possible, to print at least a warning message during install, as happen 
when you upgrade a kernel using the same version.

Regards.

Cesare.

Message #20 received at 314819@bugs.debian.org (full text, mbox, reply):

From: Cesare Leonardi <celeonar@tiscali.it>

To: 314819@bugs.debian.org

Subject: Bug can be closed?

Date: Sat, 11 Feb 2006 22:16:20 +0100

Since now seems to be clear that this not a ifupdown bug, i think it can 
be closed.

Regards.

Cesare.

Message #25 received at 314819@bugs.debian.org (full text, mbox, reply):

From: Ivo Wever <ivo.wever@gmail.com>

To: 314819@bugs.debian.org

Subject: Please mark as invalid

Date: Sat, 17 Oct 2009 23:43:29 +0200

Hello,

As Cesare said, this bugreport was wrongly reported against ifupdown. It 
should have been reported against zeroconf. Please mark it as invalid.

best regards,
-- 
Ivo

Message #30 received at 314819@bugs.debian.org (full text, mbox, reply):

From: Eric Valette <eric.valette@free.fr>

To: 314819@bugs.debian.org

Subject: Same problem on my NAS (but no console so worse)

Date: Sat, 11 Sep 2010 22:38:53 +0200

Same symptom but no zeroconf installed.

-- eric

Message #35 received at 314819@bugs.debian.org (full text, mbox, reply):

From: Eric Valette <Eric.Valette@Free.fr>

To: 314819@bugs.debian.org

Subject: The ifup eth0 or even ifup lo fails but the same command using strace -f works

Date: Mon, 13 Sep 2010 10:52:51 +0200

As subject says, its a weird problem, as neither the config file is 
broken but changing timing slightly make it work. It fails alaos with lo 
so it is not a driver problem. I guess the way to determine the 
interface has chnaged slightly due to libc chnage.

BTW there are a couple of use before set during the compilation, just in 
the area of the target_inteface variables.

-- eric

Message #40 received at 314819@bugs.debian.org (full text, mbox, reply):

From: "Andrew O. Shadoura" <bugzilla@tut.by>

To: Eric.Valette@free.fr

Cc: 314819@bugs.debian.org

Subject: Re: The ifup eth0 or even ifup lo fails but the same command using strace -f works

Date: Thu, 28 Oct 2010 21:39:34 +0300

[Message part 1 (text/plain, inline)]

Hello.

On Monday 13 September 2010 11:52:51 Eric Valette wrote:
> As subject says, its a weird problem, as neither the config file is
> broken but changing timing slightly make it work. It fails alaos with lo
> so it is not a driver problem. I guess the way to determine the
> interface has chnaged slightly due to libc chnage.
> 
> BTW there are a couple of use before set during the compilation, just in
> the area of the target_inteface variables.

Eric, have you found a work-around for your issue? Or, any details?

-- 
WBR, Andrew

[signature.asc (application/pgp-signature, inline)]

Message #45 received at 314819@bugs.debian.org (full text, mbox, reply):

From: Eric Valette <eric.valette@free.fr>

To: 314819@bugs.debian.org

Subject: Re: The ifup eth0 or even ifup lo fails but the same command using strace -f works

Date: Thu, 28 Oct 2010 20:50:04 +0200

On 28/10/2010 20:39, Andrew O. Shadoura wrote:
> Hello.
>
> On Monday 13 September 2010 11:52:51 Eric Valette wrote:
>> As subject says, its a weird problem, as neither the config file is
>> broken but changing timing slightly make it work. It fails alaos with lo
>> so it is not a driver problem. I guess the way to determine the
>> interface has chnaged slightly due to libc chnage.
>>
>> BTW there are a couple of use before set during the compilation, just in
>> the area of the target_inteface variables.
>
> Eric, have you found a work-around for your issue? Or, any details?


Well, I dunno: I found that failing to receive an ip address for a NAS 
without any no IP interface is too dangerous (I had to ask a friend to 
solder a serial console using the relevant information I found on 
internet!).

Now I have a fixed IP address and do not use dhclient anymore on this 
machine. The strace suggest a timing problem between the hardware link 
up and the other set of command. I also saw report about lo failing on 
ubuntu when the ifupdown command failed.

--eric

Send a report that this bug log contains spam.