Bug 105436 - ifdown gives "Device does not exist"
Summary: ifdown gives "Device does not exist"
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 2
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Mads Martin Joergensen
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-18 09:16 UTC by Andreas Jaeger
Modified: 2005-08-29 14:18 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Jaeger 2005-08-18 09:16:27 UTC 
$ ifdown ath0
    ath0      device: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
    ath0      configuration: wlan-id-00:05:4e:4e:55:50
Device "ath0" does not exist.

Why do I get this last line?
Comment 1 Andreas Jaeger 2005-08-18 09:17:06 UTC 
Even stranger:

x40:~ # ifdown eth0
    eth0      device: Intel Corporation 82541GI Gigabit Ethernet Controller
    eth0      configuration: eth-id-00:0a:e4:2e:e1:99
Device "eth0" does not exist.
x40:~ # ifup eth0
    eth0      device: Intel Corporation 82541GI Gigabit Ethernet Controller
    eth0      configuration: eth-id-00:0a:e4:2e:e1:99
Starting DHCP Client Daemon on eth0... . IP/Netmask: 10.10.102.104 / 255.255.0.0
Device "eth0" does not exist.
Comment 2 Christian Zoz 2005-08-18 10:50:49 UTC 
That is a bug in /sbin/ip. Try that:
  ifup eth0
Now eth0 has v6 address
  ip -6 address flush dev eth0
This works without error, eth0 has no more v6 adress
  ip -6 address flush dev eth0
Now you get that error.

That should not hapen. If you try without '-6' you get the right message
"nothing to flush"

I now removed these lines from ifup that flush the ipv6 adresses, because it is
silly. (We just have it, because i forgot to remove it before master some
versions ago). Then you won't s get this message anymore.

Nevertheless ip is broken, we already had that problem some time ago.
Comment 3 Mads Martin Joergensen 2005-08-18 16:14:33 UTC 
The problem we had was different but looked the same
Comment 4 Mads Martin Joergensen 2005-08-29 09:49:41 UTC 
Is this problem still there with beta3?
Comment 5 Andreas Jaeger 2005-08-29 14:18:24 UTC 
Looks fixed.