Your message dated Tue, 05 Apr 2005 12:01:52 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#302615: ifupdown: "ifup -a" only brings up certain
interfaces
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 1 Apr 2005 21:53:14 +0000
>From [EMAIL PROTECTED] Fri Apr 01 13:53:13 2005
Return-path: <[EMAIL PROTECTED]>
Received: from bender.bawue.de [193.7.176.20]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DHU4n-0001gS-00; Fri, 01 Apr 2005 13:53:13 -0800
Received: by bender.bawue.de (Postfix, from userid 10)
id 9C8CC4401A; Fri, 1 Apr 2005 23:53:11 +0200 (MEST)
Received: by mobile-mx.n-dimensional.de (Postfix, from userid 1001)
id 45A4971775; Fri, 1 Apr 2005 23:51:51 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Hans Ulrich Niedermann <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: ifupdown: "ifup -a" only brings up certain interfaces
X-Mailer: reportbug 3.8
Date: Fri, 01 Apr 2005 23:51:51 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: ifupdown
Version: 0.6.4-4.12
Severity: normal
Abstract:
"ifup -a" does not handle all interfaces defined with their
own "auto" stanza.
Workaround:
Add all interfaces into a single "auto" stanza.
Detailed report:
interfaces(5) says:
Stanzas beginning with the word "auto" are used to identify the
physical interfaces to be brought up when ifup is run with the
-a option. (This option is used by the system boot scripts.)
Physical interface names should follow the word "auto" on the
same line. There can be multiple "auto" stanzas. ifup brings
the named interfaces up in the order listed.
So it should not make a difference whether the interfaces are defined
within the same "auto" stanza or in seperate stanzas.
In our case, we have the interfaces lo, eth0 and sixxs defined within
one "auto" stanza for each in /etc/network/interfaces - but "ifup -a"
only brings up lo and eth0 and does not touch sixxs.
The /etc/network/interfaces (with the addresses changed):
-------<snip>----------------------------------------------------------
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 10.0.0.1
netmask 255.0.0.0
network 10.0.0.0
broadcast 10.255.255.255
auto sixxs
iface sixxs inet6 v4tunnel
address 2001:1111:1111:2222::2
netmask 64
local 10.0.0.1
endpoint 10.0.0.2
ttl 64
up ip link set mtu 1280 dev sixxs
up ip -6 route add default via 2001:1111:1111:2222::1 dev sixxs
-------<snip>----------------------------------------------------------
If, however, we comment out all those "auto" stanzas and add a single
one
auto lo eth0 sixxs
at the beginning of the /etc/network/interfaces file, "ifup -a" now
brings up all three devices lo, eth0, and sixxs.
A comparison test with "ifdown -a" suggests that "ifdown -a" behaves
according to interfaces(5) and does not make that distinction.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages ifupdown depends on:
ii debconf [debconf-2.0] 1.4.30.11 Debian configuration management sy
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii net-tools 1.60-10 The NET-3 networking toolkit
-- debconf information:
ifupdown/convert-interfaces: true
---------------------------------------
Received: (at 302615-done) by bugs.debian.org; 5 Apr 2005 05:46:09 +0000
>From [email protected] Mon Apr 04 22:46:09 2005
Return-path: <[email protected]>
Received: from azure.humbug.org.au (azure.erisian.com.au) [66.179.181.62]
(Debian-exim)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DIgt6-0005hs-00; Mon, 04 Apr 2005 22:46:09 -0700
Received: from localhost ([127.0.0.1])
by azure.erisian.com.au with esmtpa (Exim 4.44 #1 (Debian))
id 1DIdO6-0000Wp-Ay; Tue, 05 Apr 2005 12:01:55 +1000
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 05 Apr 2005 12:01:52 +1000
From: Anthony Towns <[email protected]>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Hans Ulrich Niedermann <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#302615: ifupdown: "ifup -a" only brings up certain interfaces
References: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Hans Ulrich Niedermann wrote:
> Package: ifupdown
> Version: 0.6.4-4.12
> Severity: normal
> "ifup -a" does not handle all interfaces defined with their
> own "auto" stanza.
Sure it does :)
> In our case, we have the interfaces lo, eth0 and sixxs defined within
> one "auto" stanza for each in /etc/network/interfaces - but "ifup -a"
> only brings up lo and eth0 and does not touch sixxs.
My guess would be that ifup already thought sixxs was up based on
/etc/network/ifstate not being properly cleared. You can see what
interfaces ifupdown /thinks/ are up by cat'ing that file (or, if you
upgrade to the version in unstable, by cat'ing /etc/network/run/ifstate
instead).
The only other possibility I can see is that the "auto sixxs" line
didn't match the "iface sixxs" line (because one was written "sixs" eg).
If this is still a problem and you get any more information on this,
please feel free to reopen or refile. For now, I'm closing this report.
Cheers,
aj
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
