ifdown does not down the interface

Bug #354627 reported by Paul Larson
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
connman (Ubuntu)
Won't Fix
Undecided
Unassigned
Declined for Lucid by Sebastien Bacher
ifupdown (Ubuntu)
Invalid
Undecided
Unassigned
Declined for Lucid by Sebastien Bacher
linux (Ubuntu)
Invalid
Undecided
Unassigned
Declined for Lucid by Sebastien Bacher

Bug Description

Binary package hint: ifupdown

This is on UNR Jaunty daily build that I am testing at the moment.

plars@eee900:~$ sudo ifup eth0
Ignoring unknown interface eth0=eth0.
plars@eee900:~$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:22:15:70:9b:55
          inet addr:192.168.1.75 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::222:15ff:fe70:9b55/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:49829 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5526 errors:0 dropped:0 overruns:0 carrier:4
          collisions:0 txqueuelen:1000
          RX bytes:12483856 (12.4 MB) TX bytes:346422 (346.4 KB)
          Memory:fbfc0000-fc000000

ifupdown-0.6.8ubuntu19

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: ifupdown 0.6.8ubuntu19
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SourcePackage: ifupdown
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
Paul Larson (pwlars) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Paul,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 354627

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Simone F. (fittabile) wrote :

~$ route
Tabella di routing IP del kernel
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default pp.lan 0.0.0.0 UG 0 0 0 eth0
~$ sudo ifdown eth0
ifdown: interface eth0 not configured
~$ sudo ifup eth0
Ignoring unknown interface eth0=eth0.
~$ route
Tabella di routing IP del kernel
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default pp.lan 0.0.0.0 UG 0 0 0 eth0

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in ifupdown (Ubuntu):
status: New → Confirmed
Revision history for this message
Simone F. (fittabile) wrote :

I am on Lucid with latest kernel available in main.
I tried `apport-collect -p linux 354627`
but it says I am not able to do it since I am not in the bug report (??).
See attached message scr.ot

Revision history for this message
Simone F. (fittabile) wrote :
Revision history for this message
Simone F. (fittabile) wrote :

Tested with latest mainline kernel: confirmed bug.

uname -a
Linux lapbox 2.6.34-999-generic #201004251005 SMP Sun Apr 25 10:05:58 UTC 2010 i686 GNU/Linux

tags: removed: needs-upstream-testing
Revision history for this message
Simone F. (fittabile) wrote :

See also BUG 569796

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

iirc, UNR uses connman instead of Network Manager - this indicates that the network interface hasn't been added to ifstate, so "ifup" cannot see it

Changed in ifupdown (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Simone F. (fittabile) wrote :

@Scott James Remnant

I am not sure why you refer to connman, but I am on ubuntu Lucid (Kubuntu 9.10 => 10.04 now) and I have nnot connman installed, but ifupdown. See also BUG 569796 for additional data about my configuration. I think it needs to be reopened until it is clearly explained if I ifupdown is superseded or I have some misconfiguration in dhclient*

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote : Re: [Bug 354627] Re: ifdown does not down the interface

On Sun, 2010-04-25 at 21:56 +0000, Simone F. wrote:

> I am not sure why you refer to connman, but I am on ubuntu Lucid
> (Kubuntu 9.10 => 10.04 now) and I have nnot connman installed, but
> ifupdown. See also BUG 569796 for additional data about my
> configuration. I think it needs to be reopened until it is clearly
> explained if I ifupdown is superseded or I have some misconfiguration in
> dhclient*
>
ifupdown is only used by default in server installations; in Desktop
installations (including Kubuntu and Ubuntu, UNR, UNE, etc.) we use
software such as Network Manager and ConnMan.

Scott
--
Scott James Remnant
<email address hidden>

Revision history for this message
Simone F. (fittabile) wrote :

Sorry to be ignorant but still I do not relate the things:
I have installed ifupdown package beause of dependencies of ubuntu-minimal metapackage (which depends directly on it and on upstart which in turn depends on it too).

That said, ifupdown pkg contains ifup and ifdown scripts which thus reside on my system (/sbin/if{up,down} as per default install.
Now when I run those commands they do not succeed in doing what they are supposed to do. Would not this be a bug on ifupdown package? Is not this a desktop issue, too?

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

On Mon, 2010-04-26 at 12:56 +0000, Simone F. wrote:

> That said, ifupdown pkg contains ifup and ifdown scripts which thus reside on my system (/sbin/if{up,down} as per default install.
> Now when I run those commands they do not succeed in doing what they are supposed to do. Would not this be a bug on ifupdown package? Is not this a desktop issue, too?
>
No, it's a bug in whatever package brought up the interface for not
installing compatibility so that you can bring it down with "ifdown"

Scott
--
Scott James Remnant
<email address hidden>

Revision history for this message
Simone F. (fittabile) wrote :

So Scott, please pardon me if I insist in keeping up the questions is there any compatibility bug in net-tools? Because I also could manually call /sbin/ifconfig together with ifup ifdown but:
tst@lapbox:~/SVN$ sudo ifconfig eth0 down
[sudo] password for tst:
tst@lapbox:~/SVN$ sudo ifup eth0
ifup: interface eth0 already configured
tst@lapbox:~/SVN$ route
Tabella di routing IP del kernel
Destination Gateway Genmask Flags Metric Ref Use Iface
tst@lapbox:~/SVN$ sudo ifconfig eth0 up
tst@lapbox:~/SVN$ sudo ifdown eth0
Ignoring unknown interface eth0=eth0.
tst@lapbox:~/SVN$ route
Tabella di routing IP del kernel
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 * 255.255.255.0 U 1 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default pp.lan 0.0.0.0 UG 0 0 0 eth0

As for console commands it would seem incompatible system.-wide. If it is not going to be fixed for Lucide release, could you point me to some documentation for fixining it myself? Maybe connman website and community?

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

On Mon, 2010-04-26 at 19:05 +0000, Simone F. wrote:

> So Scott, please pardon me if I insist in keeping up the questions is
> there any compatibility bug in net-tools? Because I also could
> manually call /sbin/ifconfig together with ifup ifdown but:
>
This is what I'd expect to see. ifdown can only bring down an interface
brought up with "ifup" - not by hand.

> As for console commands it would seem incompatible system.-wide. If it
> is not going to be fixed for Lucide release, could you point me to some
> documentation for fixining it myself? Maybe connman website and
> community?
>
I don't know anything about it, sorry. I just know that this isn't an
ifupdown bug, and have passed it along so a different developer who
knows more can pick it up.

Scott
--
Scott James Remnant
<email address hidden>

Revision history for this message
Kalle Valo (kvalo) wrote :

I don't foresee that we will add ifupdown support to connman. Marking bug as wontfix.

Changed in connman (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.